This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug lto/53282] [lto w/o linker plugin] visibility-inlines-hidden makes "wrongly" hidden symbols and in a way that depends on the order of the input compilation units


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53282

--- Comment #16 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-10 09:45:47 UTC ---
(In reply to comment #15)
> I'm indeed using a "ld" that is not the one of the system.
> 
> googling around I found this:
> http://comments.gmane.org/gmane.comp.gcc.help/41304
> titled" g++: error: -fuse-linker-plugin is not supported in this configuration"
> at some point it hints to the fact the gcc configure seems to ignore the ld in
> the path
> and uses the system one, detects no plugin etc.
> 
> 
> I configured gcc with --with-ld=/usr/local/bin/ld and it does not help
> LD=/usr/local/bin/ld  neither.
> 
> I'm sure that plugin is supported by this version of ld.
> I wil try more, any suggestion is appreciated.
> 
> 
> in the mean time  we can change the bug report saying that it happens if the
> linker-plugin is not usedâ

I think you need to use --with-plugin-ld.  Looking at how the "default" linker
is determined it seems you would need to set DEFAULT_LINKER, at least I cannot
see how --with-ld would end up in $gcc_cv_ld (configure would need to print
your supplied ld when looking for ld and for the ld to use for the target).


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]