This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/66397] sanitize=undefined triggers extra -Warray-bounds warning
- From: "sirl at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 03 Jun 2015 12:11:56 +0000
- Subject: [Bug c/66397] sanitize=undefined triggers extra -Warray-bounds warning
- Auto-submitted: auto-generated
- References: <bug-66397-4 at http dot gcc dot gnu dot org/bugzilla/>
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 warning again. Another special casing in the
build system... From this POV I would prefer to get only the
-fsanitize=undefined runtime error.