This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/25502] I64d format Werror problem in build
- From: "joseph at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 May 2008 12:15:22 -0000
- Subject: [Bug bootstrap/25502] I64d format Werror problem in build
- References: <bug-25502-10259@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #15 from joseph at codesourcery dot com 2008-05-11 12:15 -------
Subject: Re: Werror problem in build
On Sun, 11 May 2008, aaronavay62 at aaronwl dot com wrote:
> ------- Comment #13 from aaronavay62 at aaronwl dot com 2008-05-11 03:04 -------
> What would be an acceptable solution other than having bootstrap perpetually
> broken, and other than --disable-werror?
You could disable -pedantic when bootstrapping on Windows hosts, or use
-Wno-error=format, or make it possible to control these warnings
separately with -Wno-error=format-pedantic.
> 1) We could only enable this warning when in strict mode, eg -std=c99
> -pedantic. -std=gnu99 -pedantic would not warn. This seems like it might be
> best.
This isn't how the warning options are meant to work; I don't think we
want yet more variations on when particular warnings are enabled.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502