https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66397
Marek Polacek changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66397
--- Comment #3 from Franz Sirl ---
Yeah, I feared so :-(. This is a bit unfortunate though, as for our code base
we compile with -Werror=array-bounds, now when I add -fsanitize=undefined I
need to downgrade the error to a warning again. Another s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66397
Marek Polacek changed:
What|Removed |Added
CC||mpolacek at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66397
--- Comment #1 from Andrew Pinski ---
Comment on attachment 35691
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35691
testcase, warns with gcc-6 -c -O2 -fsanitize=undefined
Except it is undefined behavior to have one element before the st
