http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47497
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.01.28 14:07:32
CC| |hubicka at gcc dot gnu.org
Ever Confirmed|0 |1
--- Comment #6 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-01-28
14:07:32 UTC ---
I can reproduce it. It seems to be an interaction of -fuse-linker-plugin
and -fwhole-program. The combinations "-fuse-linker-plugin"
and "-fwhole-program -fno-use-linker-plugin" work ok. I think mixing
linker-plugin and whole-program does not make much sense (linker-plugin
provides a more precise whole-program idea).
Honza? Why is -fwhole-program not ignored, or why should it not be?
Why does it make a difference at all here?
I can't see how the patch should cause this btw, eventually it leads to
different linker resolutions(?) or to different partitioning decisions.
The issue also reproduces with -flto-partition=1to1 (but not with =none,
though that doesn't go through the WPA path).
