http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55644
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|major |normal
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> 2013-02-15
09:42:12 UTC ---
(In reply to comment #7)
> 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.
Well, the issue is that the testing matrix with all available build-configs
is simply too large to reliably keep things working with --enable-werror.
Note that for release branches --disable-werror is the default, so you
will see extra warnings but not errors.
Normal issue, an easy workaround exists.
