This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/47891] GCC 4.6 LTO not worked reliable on Windows target
- From: "dongsheng.song at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 15 Mar 2011 03:30:16 +0000
- Subject: [Bug lto/47891] GCC 4.6 LTO not worked reliable on Windows target
- Auto-submitted: auto-generated
- References: <bug-47891-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47891
--- Comment #4 from Dongsheng Song <dongsheng.song at gmail dot com> 2011-03-15 03:30:09 UTC ---
(In reply to comment #3)
> GCC 4.6.0 also generates a correct executable with `-fno-use-linker-plugin'
> option. It's a linker bug. You can try Hongjiu Lu's linker from lto-mixed
> branch: <http://git.kernel.org/?p=devel/binutils/hjl/x86.git;a=summary>.
sure, it's OK with `-fno-use-linker-plugin'.
But I cannot found the document from page:
http://gcc.gnu.org/onlinedocs/gcc/Option-Summary.html
http://gcc.gnu.org/onlinedocs/gcc/Link-Options.html
I'm doubt whether this option disable LTO support.
Is anyone know why this bug not fixed in the official repository ?
Is there any schedule for fix this bug?