https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78186
--- Comment #2 from amker at gcc dot gnu.org --- Hmm, looks like it also causes below failures: aarch64_be-none-elf: FAIL: gcc.c-torture/execute/pr57130.c -O1 execution test FAIL: g++.dg/torture/vshuf-v8si.C -O2 execution test arm-none-eabi/-marm -march=armv7-a -mfpu=vfpv3-d16 -mfloat-abi=softfp: FAIL: c-c++-common/torture/vector-compare-1.c -O1 execution test FAIL: c-c++-common/torture/vector-compare-1.c -O2 execution test FAIL: c-c++-common/torture/vector-compare-1.c -O2 -flto -fno-use-linker-plugin -flto-partition=none execution test FAIL: c-c++-common/torture/vector-compare-1.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects execution test FAIL: c-c++-common/torture/vector-compare-1.c -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test FAIL: c-c++-common/torture/vector-compare-1.c -O3 -g execution test FAIL: c-c++-common/torture/vector-compare-1.c -Os execution test I guess bf64-1.c is easier to debug, I can verify these tests once you got a patch. Thanks, bin
