--- 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?
1) We could only enable this warning when in strict mode, eg -std=c99
-pedantic. -std=gnu99
--- Comment #10 from zuxy dot meng at gmail dot com 2008-03-19 06:43
---
Still, 4.3.0 can't recoginze %I64d
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502
--- Comment #11 from pinskia at gcc dot gnu dot org 2008-03-19 07:09
---
(In reply to comment #10)
Still, 4.3.0 can't recoginze %I64d
And that is because it is just being added:
http://gcc.gnu.org/ml/gcc-patches/2008-03/msg01109.html
--
--- Comment #12 from dannysmith at users dot sourceforge dot net
2008-03-19 21:35 ---
(In reply to comment #11)
(In reply to comment #10)
Still, 4.3.0 can't recoginze %I64d
And that is because it is just being added:
http://gcc.gnu.org/ml/gcc-patches/2008-03/msg01109.html
--- Comment #9 from pinskia at gcc dot gnu dot org 2007-07-17 21:13 ---
*** Bug 32794 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #8 from fxcoudert at gcc dot gnu dot org 2007-05-22 13:06
---
(In reply to comment #7)
I plan to follow up in stage 1 of 4.3
ping?
There was a patch for %I64 proposed here:
http://gcc.gnu.org/ml/gcc-patches/2007-04/msg00767.html
--
fxcoudert at gcc dot gnu dot org
--- Comment #6 from rmathew at gcc dot gnu dot org 2006-06-04 09:47 ---
By the way, x-mingw32 contains:
# On MinGW, we use %IA64d to print 64-bit integers, and the format-checking
# code does not handle that, so we have to disable checking here.
WERROR_FLAGS += -Wno-format
This
--- Comment #7 from dannysmith at users dot sourceforge dot net 2006-06-04
11:02 ---
In my local tree (and in the 3.4.x mingw tree), I have added a modification and
extension of this patch:
http://gcc.gnu.org/ml/gcc-patches/2004-11/msg02296.html
I plan to follow up in stage 1 of 4.3
--- 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
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last
--- 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). And anyway, it
--- Comment #1 from fxcoudert at gcc dot gnu dot org 2005-12-20 11:35
---
Same problem for gcc/cfg.c, gcc/loop-unroll.c, gcc/loop-iv.c and others. Seems
like a definition problem with HOST_WIDEST_INT_PRINT_DEC.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-12-20 16:37 ---
Would be caused by:
2005-08-23 Mark Mitchell [EMAIL PROTECTED]
* hwint.h (HOST_WIDE_INT_PRINT): Use HOST_LONG_LONG_FORMAT.
2004-11-23 Mark Mitchell [EMAIL PROTECTED]
* hwint.h
--- Comment #3 from mmitchel at gcc dot gnu dot org 2005-12-20 16:44
---
This was discussed after I posted the patch. The GCC format-checking stuff
does not know about the Windows extensions. So, on MinGW, you should
--disable-werror. This bug should be reclassified as a diagnostic
14 matches
Mail list logo