From: Ian Lance Taylor <ian@cygnus.com>
To: robertl@dgii.com
Cc: gas2@cygnus.com
Subject: Re: emulation on i386-coff, i386-elf patches
Date: Thu, 09 Jan 1997 09:06:00 -0000 [thread overview]
Message-ID: <199701091706.JAA09307@rtl.cygnus.com> (raw)
In-Reply-To: <m0viBxp-0002VuC@rjlhome.dgii.com>
Date: Wed, 8 Jan 1997 22:19:36 -0600 (CST)
From: Robert Lipe <robertl@dgii.com>
> In fact, I'm not certain that the BFD_ASSEMBLER version of the i386
> COFF assembler works correctly. You need to make sure that if you
> configure with --target i386-coff --enable-bfd-assembler the resulting
> code works.
Building that stand-alone results in it being unable to resolve:
obj_read_begin_hook read.o
obj_symbol_new_hook symbols.o
I didn't pursue that aspect further.
You can probably define both to be empty macros in tc-i386.h.
Since you and Ken both sound doubtful of BFD_ASSEMBLER on i386 COFF,
could you offer hints on suspected problem areas? Sounds like I
should take the time to get a 'make check' working.
Since you have access to an i386 COFF native system, the best check is
to run `make CC=gcc bootstrap' in the gas build directory. That will
do a three stage of gas with itself.
The problem areas will be md_apply_fix and tc_gen_reloc. You will
need to tweak them in apparently senseless fashion until they do the
right thing (you should be able to figure out what the right thing is
by looking at the object code generated by the non-BFD version).
Unfortunately, gas reloc handling is broken, and fixing it is hard.
Ian
prev parent reply other threads:[~1997-01-09 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-08 10:43 Robert Lipe
1997-01-08 10:50 ` Ian Lance Taylor
1997-01-08 12:07 ` Ken Raeburn
1997-01-08 20:20 ` Robert Lipe
1997-01-09 9:06 ` 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=199701091706.JAA09307@rtl.cygnus.com \
--to=ian@cygnus.com \
--cc=gas2@cygnus.com \
--cc=robertl@dgii.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).