[Bug c++/52954] Missing bounds check warning without optimization

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52954

--- Comment #5 from Manuel López-Ibáñez  ---
Ops, wrong PR. Try again: Duplicate.

*** This bug has been marked as a duplicate of bug 35587 ***

[Bug c++/52954] Missing bounds check warning without optimization

[manu at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52954

Manuel López-Ibáñez  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 CC||manu at gcc dot gnu.org
 Resolution|--- |DUPLICATE

--- Comment #4 from Manuel López-Ibáñez  ---
Duplicate

*** This bug has been marked as a duplicate of bug 3587 ***

[Bug c++/52954] Missing bounds check warning without optimization

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52954

Andrew Pinski  changed:

   What|Removed |Added

 CC||leis at in dot tum.de

--- Comment #3 from Andrew Pinski  ---
*** Bug 63233 has been marked as a duplicate of this bug. ***

[Bug c++/52954] Missing bounds check warning without optimization

[rguenth at gcc dot gnu.org]

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

Richard Guenther  changed:

   What|Removed |Added

   Keywords||diagnostic
 Status|UNCONFIRMED |NEW
   Last reconfirmed||2012-04-13
Summary|Missing bounds check|Missing bounds check
   |warning |warning without
   ||optimization
 Ever Confirmed|0   |1

--- Comment #2 from Richard Guenther  2012-04-13 
09:51:38 UTC ---
We only perform array-bounds warnings when we optimize and the VRP pass is
turned on.  We completely miss this kind of warning in the frontend(s),
though they for sure can only detect very simple cases.