https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65709
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> --- I'm saying that if the program does not trigger undefined behavior (e.g. by accessing misaligned integers without telling the compiler about it (by using memcpy, or packed attribute or pragma), then it would be a compiler bug to use an instruction requiring higher alignment than guaranteed in the source, without ensuring such alignment (through realigning arrays, introducing a loop for aligning pointers before the vectorized loop, peeling a few iterations needed to align the pointer(s), or using instructions that don't require such high alignment). No testcase has been provided here without having undefined behavior in them that would show a bug on the compiler side.
