------- Comment #2 from manu at gcc dot gnu dot org 2007-11-13 04:55 -------
(In reply to comment #1)
> Warnings from optimizers are semi a no-no. Yes we have them for strict
> aliasing and overflow but I think those cases are a bit weird. This is
> unspecified behavior no matter what and there is no flag to change the
> behavior
> here.
Well, Wtype-limits is supposed to warn about this and it doesn't. Can we do it
from the front-end? If not, then warning from the middle-end seems the right
thing to do as long as it is not complex/intrusive.
--
manu at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |manu at gcc dot gnu dot org
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2007-11-13 04:55:56
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33738
