[llvm-bugs] [Bug 36856] New: llvm-ranlib, llvm-nm, llvm-ar

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=36856

            Bug ID: 36856
           Summary: llvm-ranlib, llvm-nm, llvm-ar
           Product: Documentation
           Version: 6.0
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: General docs
          Assignee: unassignedbugs at nondot.org
          Reporter: dilyan.palauzov at aegee.org
                CC: llvm-bugs at lists.llvm.org

gcc-ar/gcc-nm/gcc-ranlib compared to ar/nm/ranlib provide an implicit --plugin
argument, so that the former can work with LTO objects, even when the gcc-lto
plugin is not in {libdir}/bfd-plugins.

Do llvm-ar, llvm-ranlib and llvm-nm also imply a --plugin argument, compared to
ar/ranlib/nm concerning LTO?

How should libraries be portably build with LTO?  Shall ./configure detect,
whether clang or gcc is used, and then substitute AR with llvm-ar or gcc-ar,
until llvm starts installing  LLVMgold.so under {libdir}/bfd-plugins ?

Also https://llvm.org/docs/LinkTimeOptimization.html does not say anything
about llvm-ar/llvm-nm/llvm-ranlib, only on
https://clang.llvm.org/docs/ThinLTO.html they are decently mentioned.   At the
same time under https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html gcc-ar
and gcc-ranlib are mentioned.

Finally, if two different versions of clang are installed on a system, lets'
say first clang5 is installed and then clang6. Then the install process creates
only one LLVMgold.so, which is overwriten by the second installation.  Will
then llvm-ar use that newer LLVMgold.so, even if the object file was compiled
with clang-6.0.  I do not know how gcc-ar acts in this regard, but at least the
different lto-plugins per gcc version coexist on the system in different
directories.

-- 
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/20180321/4a1861e5/attachment.html>