https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47754
--- Comment #10 from Allan Jensen <linux at carewolf dot com> --- No I mean it triggers when you compile with -mavx2, it is solved with -march=haswell. It appears the issue is the tune flag X86_TUNE_AVX256_UNALIGNED_LOAD_OPTIMAL is set for all processors that support avx2, but if you use generic+avx2, it still pessimistically optimizes for pre-avx2 processors setting MASK_AVX256_SPLIT_UNALIGNED_LOAD. Though since there are two controlling flags and the second X86_TUNE_AVX256_UNALIGNED_STORE_OPTIMAL is still set for some avx2 processors (btver and znver) besides generic, it is harder to argue what generic+avx2 should do there.
