http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48947
Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iant at google dot com --- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-05-12 08:51:25 UTC --- (In reply to comment #4) > I checked those errors with both binutils 2.21 release and 2.22 CVS (10th of > May). > > > gcc -### > Using built-in specs. > COLLECT_GCC=/???/x86_64-gcc-4.6.0/bin/gcc > COLLECT_LTO_WRAPPER=/???/x86_64-gcc-4.6.0/libexec/gcc/x86_64-unknown-linux-gnu/4.6.0/lto-wrapper > Target: x86_64-unknown-linux-gnu > Configured with: ../configure --prefix=/???/x86_64-gcc-4.6.0 --enable-shared > --with-arch=native --enable-languages=c,c++ --enable-lto --enable-plugin > --enable-gold --enable-linker-build-id --disable-multilib --enable-ld=default > --with-plugin-ld=ld.gold > Thread model: posix > gcc version 4.6.0 (GCC) > > If you mean CC=gcc -flto -fuse-linker-plugin, I get the same errors. With "using GNU ld" I mean configuring with --with-plugin-ld=ld.bfd (or omitting that configure option). I'm CCing a gold expert, maybe he can shed some light on that error. I suppose all object files _are_ built with -fPIC (eventually LTO takes some symbols local by making them have hidden visibility - can that cause issues?).