[Bug lto/84579] __gnu_lto_v1 should be removed when linking with -fno-lto
rguenth at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Tue Feb 27 14:23:00 GMT 2018
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84579
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |lto
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-02-27
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. This isn't easy to do given only the linker can. When using GNU ld
one might be able to use filter objects or some custom linker scripts but don't
hold your breath.
I'd rather like to see those common symbols to die completely - though that's
equally hard given they have been hardcoded into binutils meanwhile... Using
ELF notes or simply keying on section names should be possible as well. It's
only the non-linker-plugin path which uses nm to look for objects with LTO
bytecode that might be harder to fix (well, use readelf or similar tools or
simply use a simple-object handler).
More information about the Gcc-bugs
mailing list