https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80925
--- Comment #16 from rdapp at linux dot vnet.ibm.com --- (In reply to seurer from comment #14) > spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-test/gcc/xgcc > -B/home/seurer/gcc/build/gcc-test/gcc/ > /home/seurer/gcc/gcc-test/gcc/testsuite/gcc.dg/vect/vect-33-big-array.c > -fno-diagnostics-show-caret -fdiagnostics-color=never -maltivec > -mpower8-vector -ftree-vectorize -fno-vect-cost-model -fno-common -O2 > -fdump-tree-vect-details -S -o vect-33-big-array.s > PASS: gcc.dg/vect/vect-33-big-array.c (test for excess errors) > PASS: gcc.dg/vect/vect-33-big-array.c scan-tree-dump-times vect "vectorized > 1 loops" 1 > FAIL: gcc.dg/vect/vect-33-big-array.c scan-tree-dump-times vect "Vectorizing > an unaligned access" 0 > FAIL: gcc.dg/vect/vect-33-big-array.c scan-tree-dump-times vect "Alignment > of access forced using peeling" 1 > Executing on host: /home/seurer/gcc/build/gcc-test/gcc/xgcc > -B/home/seurer/gcc/build/gcc-test/gcc/ > /home/seurer/gcc/gcc-test/gcc/testsuite/gcc.dg/vect/vect-33-big-array.c > -fno-diagnostics-show-caret -fdiagnostics-color=never -flto > -ffat-lto-objects -maltivec -mpower8-vector -ftree-vectorize > -fno-vect-cost-model -fno-common -O2 -fdump-tree-vect-details -S -o > vect-33-big-array.s (timeout = 300) There is still -mpower8-vector in the compile options, making unaligned stores inexpensive. This is really run on a power6 CPU? In order to bulk-disable tests that rely on peeling, would something like a global check (e.g. target_vect_unaligned, akin to target_vect_int etc.) make sense? This could be used to flag and disable specific tests depending on the CPU the the vect suite is run on.
