This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Add ld.gold option "--dynamic-list-only"


> Why do we need a new option?

The problem that --dynamic-list doesn't modify automatic exports (what
is already exported by __attribute__((visibility( default ))) ) and
there is no way to override automatic exports.

But this is not necessary if bug with --exclude-libs is fixed. The bug
is that --exclude-libs overrides exports specified by --dynamic-list
or --export-symbol (non-automatic exports).


On Tue, Mar 11, 2014 at 4:47 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Tue, Mar 11, 2014 at 1:26 PM, Cary Coutant <ccoutant@google.com> wrote:
>> The binutils list got dropped accidentally from our conversation.
>> Here's the missing part of the conversation...
>>
>> Does anyone have any comment on whether a symbol that is both in
>> --dynamic-list script and in an --exclude-libs library should be
>> exported? I think it's a bug that --exclude-libs overrides
>> --dynamic-list -- the other way around is the only way that makes
>> sense to me.
>>
>
> Doesn't version script
>
>    Node name can be omitted, provided it is the only version node in the
> version script.  Such version script doesn't assign any versions to
> symbols, only selects which symbols will be globally visible out and
> which won't.
>
>      { global: foo; bar; local: *; };
>
> do the same thing?  Why do we need a new option?
>
>
> --
> H.J.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]