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.
