From: Alan Modra <alan@linuxcare.com.au>
To: "H . J . Lu" <hjl@valinux.com>
Cc: binutils@sourceware.cygnus.com
Subject: Re: Can we emulate i386-pc-pe-coff with i386coff?
Date: Wed, 14 Jun 2000 19:48:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0006151243270.11751-100000@front.linuxcare.com.au> (raw)
In-Reply-To: <20000614110753.A2720@valinux.com>
On Wed, 14 Jun 2000, H . J . Lu wrote:
> I don't think we can emulate i386-pc-pe-coff with i386coff. I don't
> even know we can emulate i386-pc-pe-coff at all. The problem is
> config/tc-i386.c has #ifdef TE_PE inside. We need to modify it to
> check TE_PE at the runtime or do something else. Anyway, this patch
> disable the i386coff emulation for i386-pc-pe-coff.
Agreed. I dislike all those #ifdefs. What's really needed is an overhaul
of the generic reloc handling code so that all the back-end fudges can be
removed. A major undertaking.
--
Linuxcare. Support for the Revolution.
next prev parent reply other threads:[~2000-06-14 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-14 11:08 H . J . Lu
2000-06-14 19:48 ` Alan Modra [this message]
2000-06-18 9:41 ` My i386-pc-pe-coff pacth to gas/configure.in [Re: Can we emulate i386-pc-pe-coff with i386coff?] H . J . Lu
2000-06-16 7:54 ` New cross toolchain development utility Steve Hill
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=Pine.LNX.4.21.0006151243270.11751-100000@front.linuxcare.com.au \
--to=alan@linuxcare.com.au \
--cc=binutils@sourceware.cygnus.com \
--cc=hjl@valinux.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).