--- Begin Message ---On Tue, Mar 21, 2023 at 12:35:19PM +0000, Andrew Stubbs wrote: > > @@ -82,8 +82,7 @@ main () > > /* 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, committed as obvious: 2023-03-21 Jakub Jelinek <ja...@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. --- gcc/testsuite/gcc.dg/vect/vect-simd-clone-16.c.jj 2023-03-21 13:28:47.062298853 +0100 +++ gcc/testsuite/gcc.dg/vect/vect-simd-clone-16.c 2023-03-21 13:40:04.714486518 +0100 @@ -80,8 +80,7 @@ main () 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. */ --- gcc/testsuite/gcc.dg/vect/vect-simd-clone-17.c.jj 2023-03-21 13:28:47.062298853 +0100 +++ gcc/testsuite/gcc.dg/vect/vect-simd-clone-17.c 2023-03-21 13:40:15.387331984 +0100 @@ -80,8 +80,7 @@ main () 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. */ --- gcc/testsuite/gcc.dg/vect/vect-simd-clone-18.c.jj 2023-03-21 13:28:47.063298839 +0100 +++ gcc/testsuite/gcc.dg/vect/vect-simd-clone-18.c 2023-03-21 13:40:25.894179841 +0100 @@ -80,8 +80,7 @@ main () 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. */ Jakub
--- End Message ---
[jakub@redhat.com: Re: [PATCH] testsuite: Fix up vect-simd-clone1[678]*.c tests [PR108898]]
Jakub Jelinek via Gcc-patches Tue, 21 Mar 2023 05:46:21 -0700