On Tue, Mar 21, 2023 at 12:35:19PM +0000, Andrew Stubbs wrote:
> > /* Ensure the the in-branch simd clones are used on targets that support them.
> > Some targets use another call for the epilogue loops. */
> > -/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 2 "vect" { target { ! aarch64*-*-* } } } } */
> > -/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 3 "vect" { target aarch64*-*-* } } } */
> > +/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 2 "vect" } } */
>
> I suppose those comments are now obsolete.
Oops, fixed thusly.
2023-03-21 Jakub Jelinek <jakub@redhat.com>
PR testsuite/108898
* gcc.dg/vect/vect-simd-clone-16.c: Remove parts of comment mentioning
epilogue loops.
* gcc.dg/vect/vect-simd-clone-17.c: Likewise.
* gcc.dg/vect/vect-simd-clone-18.c: Likewise.
return 0;
}
-/* Ensure the the in-branch simd clones are used on targets that support them.
- Some targets use another call for the epilogue loops. */
+/* Ensure the the in-branch simd clones are used on targets that support them. */
/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 2 "vect" } } */
/* The LTO test produces two dump files and we scan the wrong one. */
return 0;
}
-/* Ensure the the in-branch simd clones are used on targets that support them.
- Some targets use another call for the epilogue loops. */
+/* Ensure the the in-branch simd clones are used on targets that support them. */
/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 2 "vect" } } */
/* The LTO test produces two dump files and we scan the wrong one. */
return 0;
}
-/* Ensure the the in-branch simd clones are used on targets that support them.
- Some targets use another call for the epilogue loops. */
+/* Ensure the the in-branch simd clones are used on targets that support them. */
/* { dg-final { scan-tree-dump-times {[\n\r] [^\n]* = foo\.simdclone} 2 "vect" } } */
/* The LTO test produces two dump files and we scan the wrong one. */