[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gold/18703] Symbol version and Version script incompatibility with

From: hjl.tools at gmail dot com
Subject: [Bug gold/18703] Symbol version and Version script incompatibility with BFD ld
Date: Wed, 22 Jul 2015 00:53:14 +0000


--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Cary Coutant from comment #6)
> >    Another usage of the '.symver' directive is:
> >      .symver NAME, NAME2@@NODENAME
> >    In this case, the symbol NAME must exist and be defined within the
> > file being assembled.  It is similar to address@hidden  The difference
> > is NAME2@@NODENAME will also be used to resolve references to NAME2 by
> > the linker.
> >
> > Linker shouldn't use address@hidden to resolve references to foo.
> Yes, I understand that much. The example given uses:
>    .symver foo, address@hidden
> where the original symbol and the versioned symbol both have the same
> name. This produces two symbols in the .o file named "foo":
> 0000000000000000 T foo
> 0000000000000000 T address@hidden
> With the version script, gold sees the first of those (plain "foo")
> and makes it the default version (as, I think, it should). The second
> one is just seen as a second declaration, but it's already been marked
> the default.

foo is versioned and only version specified is VERS_1.1, which is not
default version.  It is wrong to create a default foo without being asked
to do so.

You are receiving this mail because:
You are on the CC list for the bug.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]