https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120980
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Hmm, I didn't consider the case where the access as the vectorizer views it (the 4 element "vector") has to be split due to target implementation concerns. We do not want to introduce additional code generation overhead to avoid a fully out-of-bounds but known not trapping because it's known to fall into the same page as a previous partly not out-of-bounds access. But I realize this altered constraint might be difficult to implement in the analysis tool? This might also happen outside of early break vectorization.
