All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: 16bit x86 assembler/disassembler
Date: Sat, 26 Sep 2009 11:21:53 +0200	[thread overview]
Message-ID: <1253956913.2804.11.camel@fz.local> (raw)
In-Reply-To: <ad2655cb0909251425p5cce9ca1s9c1d3e526c673796@mail.gmail.com>

Am Freitag, den 25.09.2009, 22:25 +0100 schrieb James Courtier-Dutton:
> 2009/9/25 Seth Goldberg <Seth.Goldberg@sun.com>:
> > Hi,
> >
> >  gas supports 16-bit code with .code16 directives.  What are you trying to
> > do?
> >
> 
> I would like to have some .c code, compile it into 16-bit x86 code. I
> then want to look at the resulting 16-bit x86 code with a
> disassembler.

This is totally off topic to this list.
If you want to see what asm code gcc generates just use gcc with -S
option and the asm code gets stored in an .s file

Debian has x86dis packaged, which seems to be an x86 disassembler.

But please don't continue that topic on this list.
Search another place to get help, this has absolutely nothing to do with
GRUB specific development.

-- 
Felix Zielcke
Proud Debian Maintainer




  reply	other threads:[~2009-09-26  9:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-25 21:07 16bit x86 assembler/disassembler James Courtier-Dutton
2009-09-25 21:10 ` Seth Goldberg
2009-09-25 21:25   ` James Courtier-Dutton
2009-09-26  9:21     ` Felix Zielcke [this message]
2009-09-25 22:29   ` configure does not honor CC when testing for -mcmodel=large Seth Goldberg
2009-09-25 22:35     ` Seth Goldberg
2009-09-25 23:01       ` Colin Watson
2009-09-26 14:28         ` Vladimir 'phcoder' Serbinenko
2009-09-25 22:37     ` Colin Watson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1253956913.2804.11.camel@fz.local \
    --to=fzielcke@z-51.de \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.