From: "H. J. Lu" <hjl@lucon.org>
To: binutils@sources.redhat.com
Subject: RFC: Remove output_target in ld
Date: Mon, 22 May 2006 08:45:00 -0000 [thread overview]
Message-ID: <20060521223002.GB16551@lucon.org> (raw)
ld has both output_target and ld_emulation, which has a target_name
field. Both of them are supposed to specify the output target name.
However, they aren't consistent, especially when a linker supports
different endians. Why do we need output_target? Can we set
ld_emulation correctly and use ld_emulation->target_name to replace
output_target. Also ld supports the GNUTARGET enviroment variable.
But we don't use it to set ld_emulation. I'd like to modify ld to
make ld_emulation consistent:
1. Initialize ld_emulation properly with
a. GNUTARGET.
b. -m EMULATION.
and correct endian, based on -EL/-BL.
2. Use ld_emulation->target_name to identify the output target.
H.J.
next reply other threads:[~2006-05-21 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 8:45 H. J. Lu [this message]
2006-05-22 8:49 ` H. J. Lu
2006-05-22 8:57 ` 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=20060521223002.GB16551@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@sources.redhat.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).