[llvm-bugs] [Bug 34012] --no-undefined-version fails with version aliases

via llvm-bugs llvm-bugs at lists.llvm.org
Wed Aug 2 14:16:12 PDT 2017


Shoaib Meenai <smeenai at fb.com> changed:

           What    |Removed                     |Added
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED

--- Comment #1 from Shoaib Meenai <smeenai at fb.com> ---
Having looked into this more, I'm less convinced that it's a bug. Non-default
versioned symbols aren't used to resolve referenced to the unversioned symbol
(e.g. if I have a library providing f at V1 and an executable referencing f and
linking against the library, f at V1 won't resolve the reference to f), so it
seems fair for version scripts to behave the same way.

I'll change the version script I was running into this issue on. I must have
been doing something wrong earlier when I thought bfd needed the global: f to
export f; it does export it even without. Closing this out accordingly.

Symbol visibility makes my head hurt.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170802/fd7fbe69/attachment.html>

More information about the llvm-bugs mailing list