This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/46502] collect2 LTO marker detection is fragile wrt. to nm output format
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 07 May 2012 11:57:34 +0000
- Subject: [Bug lto/46502] collect2 LTO marker detection is fragile wrt. to nm output format
- Auto-submitted: auto-generated
- References: <bug-46502-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46502
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-05-07
Ever Confirmed|0 |1
--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-07 11:57:34 UTC ---
Confirmed. This issue is still present - even the LTO linker plugin identifies
files via that mechanism :/
Looks like simple things "stick" ...
libiberties simple-object could be used to instead query for a
.gnu.lto_.opts section.
The collect2 issue might eventually be "fixed" by making LTO require using
the linker-plugin path.