This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/25502] Werror problem in build
- From: "mark at codesourcery dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 22 Dec 2005 08:19:37 -0000
- Subject: [Bug bootstrap/25502] Werror problem in build
- References: <bug-25502-10259@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from mark at codesourcery dot com 2005-12-22 08:19 -------
Subject: Re: Werror problem in build
fxcoudert at gcc dot gnu dot org wrote:
> ------- Comment #4 from fxcoudert at gcc dot gnu dot org 2005-12-22 07:35 -------
> (In reply to comment #3)
>
>>So, on MinGW, you should --disable-werror.
>
>
> I can understand the why, but I don't think it should be required (because that
> means other warnings will not be spotted).
There is no way around this; if you do not use the special Microsoft
formats you will not get incorrect results; there are places where GCC
must print a 64-bit integer, especially when configured with 64-bit
HOST_WIDE_INTs, which is required for some targets.
> And anyway, it should at least be release-noted.
Good idea! Care to submit a patch for the caveats page?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502