From: Robert Lipe <robertl@dgii.com>
To: gas2@cygnus.com
Subject: Re: emulation on i386-coff, i386-elf patches
Date: Wed, 08 Jan 1997 20:20:00 -0000 [thread overview]
Message-ID: <m0viBxp-0002VuC@rjlhome.dgii.com> (raw)
In-Reply-To: <9701081850.AA12331@tweedledumb.cygnus.com>
> It looks to me like you need to hack md_apply_fix3 in tc-i386.c. In
> general, anything that does an #ifdef OBJ_ELF or #ifdef OBJ_COFF will
> have to be hacked.
Excellent catch, Ian.
Carving up tc-i386.c gave me exactly the results I needed. The ELF
emulation mode of the assembler seems to be in excellent shape. I just
watched the COFF side trip over itself, but the failure case needs trimmed
up considerably:
$ make CC='gcc ' CFLAGS=-g
gcc -c -I. -I../../gas-961217/binutils -I../bfd -I../../gas-961217/binutils/../
bfd -I../../gas-961217/binutils/../include -g ../../gas-961217/binutils/prdbg.c
gcc -g -o objdump objdump.o prdbg.o rddbg.o debug.o stabs.o ieee.o rdcoff.o -
L../bfd -lbfd -L../opcodes -lopcodes bucomm.o version.o filemode.o -L../bfd -lbf
d ../libiberty/libiberty.a
ld: line nbr entry (1125 0) found for non-relocatable symbol: section .text, fil
e prdbg.o
Note: this isn't GNU ld.
Rebuilding that specific file without -g makes it go away. I'll pursue.
> 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.
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.
Thanx, guys.
RJL
next prev parent reply other threads:[~1997-01-08 20:20 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 [this message]
1997-01-09 9:06 ` 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:
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=m0viBxp-0002VuC@rjlhome.dgii.com \
--to=robertl@dgii.com \
--cc=gas2@cygnus.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).