With the recent change to more reliably not vectorize code already
using vector types we run into FAILs of gcc.dg/vect/pr71264.c
The testcase was added for fixing an ICE and possible (re-)vectorization
of the code isn't really supported and I suspect might even go
wrong for non-bitops.
The following leaves the testcase as just testing for an ICE.
Pushed.
PR tree-optimization/110544
* gcc.dg/vect/pr71264.c: Remove scan for vectorization.
---
gcc/testsuite/gcc.dg/vect/pr71264.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/gcc/testsuite/gcc.dg/vect/pr71264.c
b/gcc/testsuite/gcc.dg/vect/pr71264.c
index 1381e0ed132..b372c00832a 100644
--- a/gcc/testsuite/gcc.dg/vect/pr71264.c
+++ b/gcc/testsuite/gcc.dg/vect/pr71264.c
@@ -1,5 +1,4 @@
/* { dg-do compile } */
-/* { dg-require-effective-target vect_int } */
typedef unsigned char uint8_t;
typedef uint8_t footype __attribute__((vector_size(4)));
@@ -18,5 +17,3 @@ void test(uint8_t *ptr, uint8_t *mask)
__builtin_memcpy(&ptr[i], &temp, sizeof(temp));
}
}
-
-/* { dg-final { scan-tree-dump "vectorized 1 loops in function" "vect" { xfail
{ { s390*-*-* sparc*-*-* } || vect32 } } } } */
--
2.35.3
