From: Ian Lance Taylor <iant@google.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Cary Coutant <ccoutant@google.com>,
Joern Rennecke <amylaar@spamcop.net>, "Ansari\,
Zia" <zia.ansari@intel.com>, GCC Development <gcc@gcc.gnu.org>,
GNU C Library <libc-alpha@sourceware.org>,
Binutils <binutils@sourceware.org>
Subject: Re: RFC: Add STB_GNU_SECONDARY
Date: Sat, 21 Apr 2012 00:49:00 -0000 [thread overview]
Message-ID: <mcrsjfx6h9t.fsf@dhcp-172-18-216-180.mtv.corp.google.com> (raw)
In-Reply-To: <CAMe9rOqO0Rhk7zv1zW8+bbYNck1wr=LAN0L6TCPEe8mYFNoENw@mail.gmail.com> (H. J. Lu's message of "Fri, 20 Apr 2012 16:51:17 -0700")
"H.J. Lu" <hjl.tools@gmail.com> writes:
> In our usage, the backup definition may not be at the end of
> command line since it may reference library symbols.
You could write out the backup function you need under a different name.
Then have the backup symbol at the end of the link call the new name of
the backup function.
I agree that this kind of approach is less convenient, but this doesn't
seem like a persuasive choice for one of the two remaining OS-dependent
symbol binding numbers. Perhaps you should try to sell this idea to the
ELF ABI, the generic space has seven available numbers.
Ian
next prev parent reply other threads:[~2012-04-21 0:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 19:47 H.J. Lu
2012-04-20 19:51 ` Roland McGrath
2012-04-20 20:11 ` H.J. Lu
2012-04-20 20:27 ` Roland McGrath
2012-04-20 20:36 ` H.J. Lu
2012-04-20 22:55 ` Petr Baudis
2012-04-20 23:30 ` H.J. Lu
2012-04-20 20:56 ` Joern Rennecke
2012-04-20 21:20 ` H.J. Lu
2012-04-20 22:11 ` Cary Coutant
2012-04-20 22:48 ` H.J. Lu
2012-04-20 22:49 ` H.J. Lu
2012-04-20 22:59 ` Ian Lance Taylor
2012-04-20 23:36 ` H.J. Lu
2012-04-20 23:40 ` Ian Lance Taylor
2012-04-20 23:51 ` H.J. Lu
2012-04-21 0:49 ` Ian Lance Taylor [this message]
2012-04-21 1:04 ` H.J. Lu
2012-04-21 1:07 ` Ian Lance Taylor
2012-04-21 1:09 ` Joern Rennecke
2012-04-21 13:53 ` H.J. Lu
2012-04-21 19:01 ` Joern Rennecke
2012-04-23 18:12 ` H.J. Lu
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=mcrsjfx6h9t.fsf@dhcp-172-18-216-180.mtv.corp.google.com \
--to=iant@google.com \
--cc=amylaar@spamcop.net \
--cc=binutils@sourceware.org \
--cc=ccoutant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=zia.ansari@intel.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).