This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: Linker exposing private symbols
- From: Jeffrey Walton <noloader at gmail dot com>
- To: Alan Modra <amodra at gmail dot com>
- Cc: Michael Matz <matz at suse dot de>, Binutils <binutils at sourceware dot org>
- Date: Mon, 3 Sep 2018 11:20:44 -0400
- Subject: Re: Linker exposing private symbols
- References: <CAH8yC8m5obs+uMMC0oVy-HMkbpAZz319fpkigxTGsnm=eX0hfA@mail.gmail.com> <20180827020613.GA10048@bubble.grove.modra.org> <CAH8yC8=eXpB67LsZY9HjZx5yXhBUVoE6iGDhRTpGgjcu64d80A@mail.gmail.com> <alpine.LSU.2.21.1808271431470.7867@wotan.suse.de> <CAH8yC8k0bai0ziAJSjyR8x3izLTTqCh0y9R99hPN8Emtt6nVtw@mail.gmail.com> <alpine.LSU.2.21.1808271538160.7867@wotan.suse.de> <CAH8yC8m-td09=YXGnr1JxKCWurx8b6FnYauufHw5VKxihDoJ4Q@mail.gmail.com> <20180828020521.GC10851@bubble.grove.modra.org>
- Reply-to: noloader at gmail dot com
On Mon, Aug 27, 2018 at 10:05 PM, Alan Modra <amodra@gmail.com> wrote:
> On Mon, Aug 27, 2018 at 12:02:58PM -0400, Jeffrey Walton wrote:
>> ...
>
> You have been told once by me and twice by Michael that the visibility
> options you are passing to gcc affect code generation, not linking.
>
> We're telling you this in the hope that it might educate you, but if
> you wish to hold on to your expectations you're free to do that. Just
> don't complain when your belief that you can walk through walls
> results in a sore nose.
Thanks everyone.
There's an open issue for GCC that hopes to close the documentation
gaps. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87190 .
Jeff