https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118891
--- Comment #15 from marcus at mc dot pp.se --- The stage1 testsuite is still running, but I'm seeing a lot of vector test failures: ---8<--- FAIL: gcc.dg/vect/pr53185-2.c execution test FAIL: gcc.dg/vect/pr56826.c execution test FAIL: gcc.dg/vect/pr57705.c execution test FAIL: gcc.dg/vect/pr57741-2.c execution test FAIL: gcc.dg/vect/pr57741-3.c execution test FAIL: gcc.dg/vect/pr91293-3.c execution test FAIL: gcc.dg/vect/vect-alias-check-10.c execution test FAIL: gcc.dg/vect/vect-alias-check-11.c execution test FAIL: gcc.dg/vect/vect-alias-check-12.c execution test FAIL: gcc.dg/vect/vect-avg-10.c execution test FAIL: gcc.dg/vect/vect-avg-9.c execution test FAIL: gcc.dg/vect/vect-gather-1.c execution test FAIL: gcc.dg/vect/vect-iv-7.c execution test FAIL: gcc.dg/vect/vect-over-widen-10.c execution test FAIL: gcc.dg/vect/vect-over-widen-11.c execution test FAIL: gcc.dg/vect/vect-over-widen-12.c execution test FAIL: gcc.dg/vect/vect-over-widen-13.c execution test FAIL: gcc.dg/vect/vect-over-widen-15.c execution test FAIL: gcc.dg/vect/vect-over-widen-19.c execution test FAIL: gcc.dg/vect/vect-over-widen-20.c execution test FAIL: gcc.dg/vect/vect-over-widen-21.c execution test FAIL: gcc.dg/vect/vect-over-widen-3-big-array.c execution test FAIL: gcc.dg/vect/vect-over-widen-3.c execution test FAIL: gcc.dg/vect/vect-over-widen-7.c execution test FAIL: gcc.dg/vect/vect-over-widen-8.c execution test FAIL: gcc.dg/vect/vect-over-widen-9.c execution test FAIL: gcc.dg/vect/vect-simd-17.c execution test FAIL: gcc.dg/vect/vect-simd-18.c execution test FAIL: gcc.dg/vect/vect-simd-19.c execution test FAIL: gcc.dg/vect/vect-simd-20.c execution test ---8<--- and the list goes on. So probably some change has been made to the vector codegen which does not handle endianness properly? I remember the last time gcc broke itself on aarch64_be was when vector code was added to cpp which didn't account for endianness.
