From: Joern Rennecke <amylaar@spamcop.net>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "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 01:09:00 -0000 [thread overview]
Message-ID: <20120420210839.ma3szz9logk4cswg-nzlynne@webmail.spamcop.net> (raw)
In-Reply-To: <CAMe9rOpNqs933DZejuBV4tjcyLnc29Z3302vkj5LN1Y23Pnzmg@mail.gmail.com>
Quoting "H.J. Lu" <hjl.tools@gmail.com>:
> We only have very few bits to in STB_XXX field.
Well, you could put the information somewhere else. E.g. a special
relocation,
or a special elf section. Or you could mangle the information into
the section name in which the symbol is present.
>> Even better, you could use symbolic tags, and have the linker script
>> assign precedence values to these tags.
>
> It won't help us.
Maybe it wouldn't buy you more than the secondary symbols right now, but
it would give a lot of flexibility to rearrange and combine different
peoples ideas of link priority.
Another thought on symbols priorities: with pthread, using symbols of
different priorities is really a crutch - and it doesn't really work
that well for static linking. What is really wanted is that
whenever one of a set of object files is linked in, a whole set of symbols
should be satisfied from a different place. Maybe if, for a static pthread,
we'd put the pthread-aware I/O etc. into a special .text.pthread section
or somesuch, which would normally discarded, but had a mechanism to use them
if a special symbol is set (or used?) from an object file that provides
a pthread API function.
next prev parent reply other threads:[~2012-04-21 1:09 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
2012-04-21 1:04 ` H.J. Lu
2012-04-21 1:07 ` Ian Lance Taylor
2012-04-21 1:09 ` Joern Rennecke [this message]
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=20120420210839.ma3szz9logk4cswg-nzlynne@webmail.spamcop.net \
--to=amylaar@spamcop.net \
--cc=binutils@sourceware.org \
--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).