public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] PR ld/18329: Turn off PROTECTED visibility with -Bsymbolic
Date: Sun, 26 Apr 2015 13:38:00 -0000	[thread overview]
Message-ID: <CAMe9rOoSZytz12GMRJdrz190Fjh3rN7V8ZdT84yFqsEQEW9-rA@mail.gmail.com> (raw)
In-Reply-To: <20150426014835.GA12627@bubble.grove.modra.org>

On Sat, Apr 25, 2015 at 6:48 PM, Alan Modra <amodra@gmail.com> wrote:
> On Sat, Apr 25, 2015 at 05:45:13PM -0700, H.J. Lu wrote:
>> On Sun, Apr 26, 2015 at 09:16:09AM +0930, Alan Modra wrote:
>> > On Sat, Apr 25, 2015 at 02:46:38PM -0700, H.J. Lu wrote:
>> > > If a global protected symbol is bound locally by -Bsymbolic, there is no
>> > > need to keep protected visibility which hich may have overhead at run-time.
>> >
>> > For this change to be safe you'd need to show that all ELF targets
>> > supporting dynamic objects also properly support -Bsymbolic for both
>> > functions and variables.  ie. that none emit dynamic relocations for
>> > the symbol when -Bsymbolic.
>> >
>>
>> Good point.  Here is a patch to make it backend dependent.  I will
>> check it in shortly.
>
> Before you do that, I'd like to know for sure what it is you're trying
> to accomplish.  I'm guessing the "may have overhead at run-time" is
> the loop over dynamic relocs in glibc/elf/dl-lookup.c:do_lookup_x.
> Correct?

I withdrew my patch.  There is no need to clear PROTECTED visibility
since there is no dynamic relocation against protected symbols in
DSOes built with -Bsymbolic.


-- 
H.J.

      reply	other threads:[~2015-04-26 13:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-25 21:46 H.J. Lu
2015-04-25 23:46 ` Alan Modra
2015-04-26  0:45   ` H.J. Lu
2015-04-26  1:48     ` Alan Modra
2015-04-26 13:38       ` H.J. Lu [this message]

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=CAMe9rOoSZytz12GMRJdrz190Fjh3rN7V8ZdT84yFqsEQEW9-rA@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    /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).