This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/53282] lto and visibility-inlines-hidden makes "wrongly" hidden symbols and in a way that depends on the order of the input compilation units
- From: "hubicka at ucw dot cz" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 09 May 2012 12:21:38 +0000
- Subject: [Bug lto/53282] lto and visibility-inlines-hidden makes "wrongly" hidden symbols and in a way that depends on the order of the input compilation units
- Auto-submitted: auto-generated
- References: <bug-53282-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53282
--- Comment #12 from Jan Hubicka <hubicka at ucw dot cz> 2012-05-09 12:21:38 UTC ---
> if I add -fuse-linker-plugin I get
> c++: error: -fuse-linker-plugin is not supported in this configuration
>
> my understanding was that since 4.6 linker-plugin was not required anymore for
> lto
No, LTO plugin is needed for "proper" LTO and will always be. We have
alternative
non-plugin path that results in poorer code quality.
In non-plugin path there is logic to privatize comdats whose address is not
taken, since they can be duplicated. With explicit instantiation this code
however should not trigger. I will check.
Honza