https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114178
--- Comment #4 from Evan Teran <evan.teran at gmail dot com> --- @Andrew, thanks for the quick analysis! Just to confirm, the warning is in fact incorrect and the emitted code is not stomping outside of the buffer bounds? I ask because I did also one last bit, which is that changing the buffer size can make the warning go away. That is if I make the buffer in the example something like 132, then it's happy again, which at the very least, makes me wonder if the vectorized code is in fact going out of bounds when the size doesn't align with the vectorized code's expectations.
