public inbox for
 help / color / mirror / Atom feed
From: Bryan Ford <>
To: Ian Lance Taylor <>
Subject: Re: fixing i386 gas for 16-bit code
Date: Thu, 20 Jun 1996 11:28:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

>   Date: Wed, 19 Jun 1996 00:41:40 -0500
>   From: VaX#n8 <>
>   I was wondering if you know how hard it would be (for me) to fix gas
>   to create 16-bit code properly, especially in the case of SIB (scaled
>   indexed based) addressing modes on the i386.
>I don't know much about the i386 myself, so I'm CC'ing your note to
>the gas developers list,  Perhaps somebody on the
>list will have some useful information.

I don't think this would really be that difficult at all;
it's just work that I didn't have enough time or motivation to do
when I added the original partial support for 16-bit code.
Probably the only changes necessary should be in tc-i386.h and the
associated header files.

>   Would I have to learn bfd?  It confused the heck outta me when I looked
>   at the bfd source last time :-/
>You shouldn't have to look at BFD for this sort of thing.

True, although there is one separate but related problem, if you're using
ELF format...  The current ELF tools (maybe the i386 ELF format period,
I don't know) don't seem to support 16-bit relocations in object files;
the assembler just dies with an error.  This can usually be worked around
by either just using 32-bit addresses in cases in which relocations are
needed, or, in single-file "programs" such as boot blocks and such,
just writing the code so that the assembler does the relocating rather
than the linker - e.g., say "foo-_start" rather than just "foo".
However, fixing this properly presumably would involve BFD hacking.


  parent reply	other threads:[~1996-06-20 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
1996-06-20  8:46 ` Ian Lance Taylor
1996-06-20 11:02   ` erich
1996-06-20 11:07   ` erich
1996-06-20 11:28   ` Bryan Ford [this message]
1996-06-20 12:16     ` Ian Lance Taylor

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:

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

  git send-email \ \ \ \ \ \

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).