[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
vincenzo.innocente at cern dot ch
gcc-bugzilla@gcc.gnu.org
Wed May 9 10:46:00 GMT 2012
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53282
--- Comment #10 from vincenzo Innocente <vincenzo.innocente at cern dot ch> 2012-05-09 10:40:08 UTC ---
On 9 May, 2012, at 12:15 PM, rguenth at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53282
>
> --- Comment #9 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-09 10:15:21 UTC ---
> Btw, the testcase does not reproduce for me. What binutils version and which
> linker do you use? Do you actually end up using -fuse-linker-plugin? Because
> it reproduces for me with -fno-use-linker-plugin only (a path that is probably
> not very well tested these days …)we use
ld -v
GNU gold (GNU Binutils 2.21.1) 1.11
and we do not use explicitely -fuse-linker-plugin,
gcc is configured as follow
c++ -v
Using built-in specs.
COLLECT_GCC=c++
COLLECT_LTO_WRAPPER=/afs/cern.ch/user/i/innocent/w3/gcc47slc5/libexec/gcc/x86_64-unknown-linux-gnu/4.7.1/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ./configure --enable-languages=c,c++,fortran
--disable-multilib --enable-gold=yes --disable-nls --enable-lto
--with-mpc=/afs/cern.ch/cms/slc5_amd64_gcc470/external/gcc/4.7.0
--with-gmp=/afs/cern.ch/cms/slc5_amd64_gcc470/external/gcc/4.7.0
--with-mpfr=/afs/cern.ch/cms/slc5_amd64_gcc470/external/gcc/4.7.0
--prefix=/afs/cern.ch/user/i/innocent/w3/gcc47slc5 : (reconfigured) ./configure
--enable-languages=c,c++,fortran --disable-multilib --enable-gold=yes
--disable-nls --enable-lto
--with-mpc=/afs/cern.ch/cms/slc5_amd64_gcc470/external/gcc/4.7.0
--with-gmp=/afs/cern.ch/cms/slc5_amd64_gcc470/external/gcc/4.7.0
--with-mpfr=/afs/cern.ch/cms/slc5_amd64_gcc470/external/gcc/4.7.0
--prefix=/afs/cern.ch/user/i/innocent/w3/gcc47slc5
Thread model: posix
gcc version 4.7.1 20120508 (prerelease) [gcc-4_7-branch revision 187276] (GCC)
>
More information about the Gcc-bugs
mailing list