This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug lto/48538] GCC build fails with -flto in BOOT_CFLAGS
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 10 Apr 2011 11:52:11 +0000
- Subject: [Bug lto/48538] GCC build fails with -flto in BOOT_CFLAGS
- Auto-submitted: auto-generated
- References: <bug-48538-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48538
--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-04-10 11:52:02 UTC ---
(In reply to comment #2)
> Ok. In the documentation it said that was equivalent to -flto in BOOT_CFLAGS,
> that's why I used it.
> Now I've checked bootstrap-lto.mk and looks like it disables lto when doing a
> profiled bootstrap. Is it right? I wonder what gives better performance: lto or
> profiled-driven optimizations...
It disables LTO during the profile instrumented stage to speed up the
compile of that. The final executables are still built with profile
feedback and LTO.