This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/55644] bootstrap-lto fails on current trunk (with and without profiledbootstrap)
- From: "matt at use dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 14 Feb 2013 18:00:57 +0000
- Subject: [Bug bootstrap/55644] bootstrap-lto fails on current trunk (with and without profiledbootstrap)
- Auto-submitted: auto-generated
- References: <bug-55644-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55644
--- Comment #7 from Matt Hargett <matt at use dot net> 2013-02-14 18:00:57 UTC ---
Sorry, but wouldn't that be "papering over bugs"? I'm confounded by the
attitude around bootstrap failures, regardless of the basic supported options
being used: -O3 with LTO and profile-use. This combination has been in use in 3
different companies I have worked with, since 4.6.x. If it's not a supported
configuration to the point where an FSF GCC release can't bootstrap itself
consistently without wrong-code/diagnostic false positives, then I'll just plan
on sticking to vendor branches -- something I don't want to do since I would
prefer not to have another EGCS situation.
Let me know how to proceed with these classes of issues.