From: Florian Weimer <fweimer@redhat.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Symbol visibility and bypassing PLT for intra-DSO calls
Date: Mon, 12 Nov 2012 15:31:00 -0000 [thread overview]
Message-ID: <50A11623.1020402@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1211121421010.2576@monoid.intra.ispras.ru>
On 11/12/2012 11:22 AM, Alexander Monakov wrote:
>> 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.
Yes, this should do it, thanks. I was confused by the
-fvisibility=protected documentation.
--
Florian Weimer / Red Hat Product Security Team
prev parent reply other threads:[~2012-11-12 15:31 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
2012-11-12 15:31 ` Florian Weimer [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=50A11623.1020402@redhat.com \
--to=fweimer@redhat.com \
--cc=amonakov@ispras.ru \
--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).