[Bug lto/46502] collect2 LTO marker detection is fragile wrt. to nm output format

gseanmcg at gmail dot com gcc-bugzilla@gcc.gnu.org
Fri Nov 25 16:39:00 GMT 2011


--- Comment #2 from Sean McGovern <gseanmcg at gmail dot com> 2011-11-25 16:32:47 UTC ---
(In reply to comment #0)
> When investigating why some users of GCC mainline on Solaris 2 saw more
> LTO-related testsuite failures than I, it turned out that collect2 calls some
> version of nm to search the object's symbol tables for __gnu_lto_v1.
> Unfortunately, this relies on the output format produced by GNU nm -n, and
> silently fails if the format is different (i.e. the LTO markers aren't found
> and lto1 isn't called).  I noticed this change between Solaris 10 (where I had
> no instance of GNU nm in PATH, neither as nm nor as gnm) and Solaris 11 (where
> there's /usr/bin/gnm in the default PATH).
> This is very fragile, hard to find, and the requirement isn't even documented.

Hi Rainer,

Has this been handled yet?

More information about the Gcc-bugs mailing list