[Bug c/66397] sanitize=undefined triggers extra -Warray-bounds warning

2015-06-22 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66397 Marek Polacek mpolacek at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[Bug c/66397] sanitize=undefined triggers extra -Warray-bounds warning

2015-06-03 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66397 --- Comment #1 from Andrew Pinski pinskia at gcc dot gnu.org --- 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

[Bug c/66397] sanitize=undefined triggers extra -Warray-bounds warning

2015-06-03 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66397 Marek Polacek mpolacek at gcc dot gnu.org changed: What|Removed |Added CC||mpolacek at

[Bug c/66397] sanitize=undefined triggers extra -Warray-bounds warning

2015-06-03 Thread sirl at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66397 --- Comment #3 from Franz Sirl sirl at gcc dot gnu.org --- 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