https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100430
Martin Sebor changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100430
--- Comment #4 from Jens Maurer ---
Thanks.
My take-away from the discussion is that -Warray-bounds triggers when there
might be a code path with bad behavior. Whether such a code path is detected
depends very much on the details of optimizatio
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100430
Martin Sebor changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100430
--- Comment #2 from Jens Maurer ---
Why does the warning go away with -O3, then? If it's intentional, it should be
consistent once the optimization level is sufficient for the necessary static
analysis.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100430
Richard Biener changed:
What|Removed |Added
Blocks||56456
Keywords|
