https://sourceware.org/bugzilla/show_bug.cgi?id=18703
--- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to Cary Coutant from comment #10) > > In this example, "foo" is both unversioned and versioned. In response > to the unversioned one, gold is creating a default version, as > directed by the linker script. If "foo@VERS_1.1" were the only version ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Linker script only specifies a version of VERS_1.1 and input file has VERS_1.1 as the non-default version. Linker shouldn't change VERS_1.1 from non-default to default. > of "foo" in this file, gold would not make it a default version. > > If you don't want a default version, get rid of the first, > unversioned, "foo", and gold will do what you expect. > > I've played around with a bunch of different combinations, and I can't > even begin to unravel the logic behind Gnu ld's behavior when there > are multiple instances of versioned and unversioned symbols. I have no > desire to try to reproduce its behavior beyond what's described in the > documentation. The documentation can have some improvements. But ld.bfd behavior is well-defined as shown by testcases in ld/testsuite/ld-elfvers. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
