public inbox for gas2@sourceware.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@cygnus.com>
To: baford@snake.cs.utah.edu
Cc: vax@linkdead.paranoia.com, gas2@cygnus.com
Subject: Re: fixing i386 gas for 16-bit code
Date: Thu, 20 Jun 1996 12:16:00 -0000	[thread overview]
Message-ID: <199606201916.PAA08087@sanguine.cygnus.com> (raw)
In-Reply-To: <199606201825.MAA17992@snake.cs.utah.edu>

   Date: Thu, 20 Jun 96 12:25:13 MDT
   From: Bryan Ford <baford@snake.cs.utah.edu>

   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.

The BFD side of this is quite trivial: in elf32-i386.c, add an entry
to enum reloc_type, elf_howto_table, and elf_i386_reloc_type_lookup.

Of course, you then have to worry about the fact that your object
files violate the ELF ABI.

Ian


      reply	other threads:[~1996-06-20 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199606190541.AAA00489@linkdead.paranoia.com>
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
1996-06-20 12:16     ` Ian Lance Taylor [this message]

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=199606201916.PAA08087@sanguine.cygnus.com \
    --to=ian@cygnus.com \
    --cc=baford@snake.cs.utah.edu \
    --cc=gas2@cygnus.com \
    --cc=vax@linkdead.paranoia.com \
    /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 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).