Adding -mmove-max=128 and -mstore-max=128 to the dg-options of the
recently added gcc.target/i386/pieces-memcmp-2.c avoids changing the
intent of this testcase when adding -march=cascadelake to RUNTESTFLAGS.
Tested on x86_64-pc-linux-gnu. Committed as obvious.
2023-06-29 Roger Sayle <[email protected]>
gcc/testsuite/ChangeLog
* gcc.target/i386/pieces-memcmp-2.c: Specify that 128-bit
comparisons are desired, to see if 256-bit instructions are
generated inappropriately (fixes test on -march=cascadelake).
diff --git a/gcc/testsuite/gcc.target/i386/pieces-memcmp-2.c
b/gcc/testsuite/gcc.target/i386/pieces-memcmp-2.c
index 6f996faeced..6061c911165 100644
--- a/gcc/testsuite/gcc.target/i386/pieces-memcmp-2.c
+++ b/gcc/testsuite/gcc.target/i386/pieces-memcmp-2.c
@@ -1,5 +1,5 @@
/* { dg-do compile { target ia32 } } */
-/* { dg-options "-O2 -mavx2" } */
+/* { dg-options "-O2 -mavx2 -mmove-max=128 -mstore-max=128" } */
int foo(char *a)
{
