[Bug bootstrap/25502] Werror problem in build

2008-05-10 Thread aaronavay62 at aaronwl dot com


--- 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 -pedantic would not warn.  This seems like it might be
best.

2) Adding __extension__ will silence this warning.  Should we make a macro to
decorate these uses of HOST_WIDEST_INT_PRINT_DEC?

3) Worse case, can we just HOST_WIDEST_INT long?


-- 

aaronavay62 at aaronwl dot com changed:

   What|Removed |Added

 CC||aaronavay62 at aaronwl dot
   ||com
   Last reconfirmed|2005-12-23 05:44:30 |2008-05-11 03:04:43
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2008-03-19 Thread zuxy dot meng at gmail dot com


--- 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



[Bug bootstrap/25502] Werror problem in build

2008-03-19 Thread pinskia at gcc dot gnu dot org


--- 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


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2008-03-19 Thread dannysmith at users dot sourceforge dot net


--- 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
 

Even with that patch, we still get 
ISO C does not support the 'I64' printf length modifier warnings because of
--predantic.  IMO, that warning is valid and useful and should not be fixed.
Danny


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2007-07-17 Thread pinskia at gcc dot gnu dot org


--- 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

 CC||gdr at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2007-05-22 Thread fxcoudert at gcc dot gnu dot org


--- 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 changed:

   What|Removed |Added

 CC||dannysmith at users dot
   ||sourceforge dot net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2006-06-04 Thread rmathew 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 should have fixed the problem, but it doesn't for some reason.

See also:

  http://gcc.gnu.org/ml/gcc-patches/2004-11/msg02223.html

(and the follow-up messages).


-- 

rmathew at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||rmathew at gcc dot gnu dot
   ||org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2006-06-04 Thread dannysmith at users dot sourceforge dot net


--- 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 

This patch silences the worst of the warnings.  However, because of the
-pedantic switch, I still get warnings like

../../gcc/gcc/gcov-dump.c:408: warning: ISO C does not support the 'I64' printf
length modifier

-Wno-pedantic-errors doesn't work for me, so --disable-werror is still
necessary.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2005-12-22 Thread mark at codesourcery dot com


--- 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



[Bug bootstrap/25502] Werror problem in build

2005-12-22 Thread pinskia at gcc dot gnu dot org


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2005-12-23 05:44:30
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2005-12-21 Thread fxcoudert at gcc dot gnu dot org


--- 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 should at least be
release-noted.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2005-12-20 Thread fxcoudert at gcc dot gnu dot org


--- 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



[Bug bootstrap/25502] Werror problem in build

2005-12-20 Thread pinskia at gcc dot gnu dot org


--- 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 (HOST_LONG_LONG_FORMAT): New macro.  Use it throughout.
* config/i386/xm-mingw32.h (HOST_LONG_LONG_FORMAT): Define. 
* doc/hostconfig.texi (HOST_LONG_LONG_FORMAT): Document.


-- 

pinskia at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||mmitchel at gcc dot gnu dot
   ||org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502



[Bug bootstrap/25502] Werror problem in build

2005-12-20 Thread mmitchel at gcc dot gnu dot org


--- 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 bug; it's a
limitation in the format checkers, not a bug in the macros.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25502