From: Jakub Jelinek <jakub@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [jakub@redhat.com: Re: [PATCH] testsuite: Fix up vect-simd-clone1[678]*.c tests [PR108898]]
Date: Tue, 21 Mar 2023 13:46:07 +0100 [thread overview]
Message-ID: <ZBmnD+dfYKuh489q@tucnak> (raw)
[-- Attachment #1: Type: text/plain, Size: 1 bytes --]
[-- Attachment #2: Type: message/rfc822, Size: 3284 bytes --]
From: Jakub Jelinek <jakub@redhat.com>
To: Andrew Stubbs <ams@codesourcery.com>
Subject: Re: [PATCH] testsuite: Fix up vect-simd-clone1[678]*.c tests [PR108898]
Date: Tue, 21 Mar 2023 13:45:54 +0100
Message-ID: <ZBmnAGIX7F4vQF0L@tucnak>
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 <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.
--- 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
reply other threads:[~2023-03-21 12:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZBmnD+dfYKuh489q@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).