public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexander Monakov <amonakov@ispras.ru>
To: Florian Weimer <fweimer@redhat.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Symbol visibility and bypassing PLT for intra-DSO calls
Date: Mon, 12 Nov 2012 10:22:00 -0000	[thread overview]
Message-ID: <alpine.LNX.2.00.1211121421010.2576@monoid.intra.ispras.ru> (raw)
In-Reply-To: <50A0BDBD.9010002@redhat.com>



On Mon, 12 Nov 2012, Florian Weimer wrote:

> On 11/12/2012 10:01 AM, Alexander Monakov wrote:
> > On Mon, 12 Nov 2012, Florian Weimer wrote:
> >
> > > Is there a way to use symbol visibility to bypass the PLT for intra-DSO
> > > calls,
> > > while still keeping the symbol public?  I don't need to support overriding
> > > the
> > > symbols from the outside, so the PLT indirection isn't needed.
> >
> > Why do you need to use the visibility mechanism specifically?  From my
> > understanding, it sounds like you can use -Bsymbolic.
> 
> It would be sort-of nice to do this at the compiler level, so that the
> programmer doesn't have to specify a linker option.  And a finer granularity
> to control this feature might make sense in some cases.

Is "protected" visibility what you need?  From the manual:

    Protected visibility is like default visibility except that it indicates
    that references within the defining module bind to the definition in that
    module. That is, the declared entity cannot be overridden by another module.

Alexander

  reply	other threads:[~2012-11-12 10:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-12  8:39 Florian Weimer
2012-11-12  9:01 ` Alexander Monakov
2012-11-12  9:13   ` Florian Weimer
2012-11-12 10:22     ` Alexander Monakov [this message]
2012-11-12 15:31       ` Florian Weimer

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=alpine.LNX.2.00.1211121421010.2576@monoid.intra.ispras.ru \
    --to=amonakov@ispras.ru \
    --cc=fweimer@redhat.com \
    --cc=gcc-help@gcc.gnu.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).