[Bug c/19977] overflow in non-static initializer should not be pedwarn

2007-01-06 Thread manu at gcc dot gnu dot org
--- Comment #6 from manu at gcc dot gnu dot org 2007-01-06 09:36 --- Fixed in mainline. -- manu at gcc dot gnu dot org changed: What|Removed |Added Status|NEW

[Bug c/19977] overflow in non-static initializer should not be pedwarn

2007-01-02 Thread manu at gcc dot gnu dot org
--- Comment #5 from manu at gcc dot gnu dot org 2007-01-02 20:07 --- Subject: Bug 19977 Author: manu Date: Tue Jan 2 20:07:44 2007 New Revision: 120355 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120355 Log: 2007-01-02 Manuel Lopez-Ibanez <[EMAIL PROTECTED]> PR c/1

[Bug c/19977] overflow in non-static initializer should not be pedwarn

2006-12-14 Thread patchapp at dberlin dot org
--- Comment #4 from patchapp at dberlin dot org 2006-12-15 01:15 --- Subject: Bug number PR c/19977 A patch for this bug has been added to the patch tracker. The mailing list url for the patch is http://gcc.gnu.org/ml/gcc-patches/2006-12/msg01068.html -- http://gcc.gnu.org/bugzilla

[Bug c/19977] overflow in non-static initializer should not be pedwarn

2006-12-09 Thread manu at gcc dot gnu dot org
--- Comment #2 from manu at gcc dot gnu dot org 2006-12-09 14:28 --- I believe that the culprit is a call to constant_expression_warning at c-typeck.c (store_init_value). The comment just above this call says "ANSI wants warnings about out-of-range constant initializers". However, if the

[Bug c/19977] overflow in non-static initializer should not be pedwarn

2005-02-15 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-15 21:20 --- Confirmed. -- What|Removed |Added Status|UNCONFIRMED |NEW E