https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108598
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Yeah, it would be good if -fanalyzer detected such issues within loops, and identified the iteration at which the access goes out-of-bounds. Handling that is bug 108432 (which I'm treating as an RFE). Thanks for the link to aufover-benchmark; taking a look now.