http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38999
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
Known to fail| |
--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-16
13:22:28 UTC ---
Since 4.7 we have need_64bit_hwint=yes for the target the bug was reported
against.
But I'm confused. Do we want two warnings here?
3.3.6 and 3.4.6 say:
/space/rguenther/install/gcc-3.3.6/bin/gcc -S -std=c99 t.c
t.c:10:13: warning: integer constant is so large that it is unsigned
t.c: In function `f':
t.c:10: warning: integer overflow in expression
while since 4.0.0 we say
t.c:10:13: warning: integer constant is so large that it is unsigned
I don't think we anywhere have a 'integer overflow in expression' warning
(not by default at least) that triggers during optimization.
So - is 4.7 fixed (because hwint 64 is default)? I didn't really check
hwint32 builds of 4.x.
