public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: <generic-abi@googlegroups.com>
Cc: <binutils@sourceware.org>
Subject: discarding rules for duplicate ELF comdat groups
Date: Tue, 01 Feb 2011 09:14:00 -0000	[thread overview]
Message-ID: <4D47DCE8020000780002FA2A@vpn.id2.novell.com> (raw)

I had originally brought this up on the binutils mailing list, but it
was suggested to bring this up in this more generic forum:

It seems like currently the rule simply is to pick the first instance the
linker gets to see. Wouldn't it make sense to honor the group
signature's attributes (namely its binding), and prefer keeping an
instance with a global group signature over a weak or local one?
That would allow the programmer some control over which
instance to keep: My main motivation is to find a way to discard
the various weak fallback functions Linux has to cover cases where
e.g. some architectures implement certain functionality, while
others that don't can all use a generic implementation.

I cannot see other mechanisms that would allow ld to discard
sections (not to speak of individual functions within sections).

Thanks, Jan

             reply	other threads:[~2011-02-01  9:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01  9:14 Jan Beulich [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-28 13:51 Jan Beulich
2011-01-28 14:07 ` H.J. Lu
2011-01-28 14:30   ` Jan Beulich
2011-01-28 14:40     ` H.J. Lu
2011-01-28 15:28       ` Jan Beulich
2011-01-28 15:56         ` H.J. Lu
     [not found]           ` <4D4305B6020000780002F372@vpn.id2.novell.com>
     [not found]             ` <AANLkTi=0RD6pYbPjXYJ3tk429WAtBa555GP1ksBedLO9@mail.gmail.com>
2011-01-31  8:02               ` Jan Beulich
2011-01-31 18:19                 ` 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=4D47DCE8020000780002FA2A@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=binutils@sourceware.org \
    --cc=generic-abi@googlegroups.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).