public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Roger Sayle <sayle@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-4244] Tweak new test cases for -march=cascadelake strangeness. Date: Fri, 8 Oct 2021 08:35:06 +0000 (GMT) [thread overview] Message-ID: <20211008083506.35EB1385840E@sourceware.org> (raw) https://gcc.gnu.org/g:90285ce98f3c69f275c05397f7c74d22462edc05 commit r12-4244-g90285ce98f3c69f275c05397f7c74d22462edc05 Author: Roger Sayle <roger@nextmovesoftware.com> Date: Fri Oct 8 09:33:38 2021 +0100 Tweak new test cases for -march=cascadelake strangeness. As reported by Sunil's tester, -march=cascadelake triggers some SUBREG non-determinacy in the generated assembler for my new tests. Fixed by updating the regular expressions to match either the zero or sign extended forms. I'm testing a backend patch that may help with the underlying cause of these differences. 2021-10-08 Roger Sayle <roger@nextmovesoftware.com> gcc/testsuite/ChangeLog * gcc.target/i386/sse2-mmx-paddsb-2.c: Test for -128 or 128. * gcc.target/i386/sse2-mmx-paddusb-2.c: Test for -1 or 255. * gcc.target/i386/sse2-mmx-psubsb-2.c: Test for -128 or 128. Diff: --- gcc/testsuite/gcc.target/i386/sse2-mmx-paddsb-2.c | 2 +- gcc/testsuite/gcc.target/i386/sse2-mmx-paddusb-2.c | 2 +- gcc/testsuite/gcc.target/i386/sse2-mmx-psubsb-2.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/gcc/testsuite/gcc.target/i386/sse2-mmx-paddsb-2.c b/gcc/testsuite/gcc.target/i386/sse2-mmx-paddsb-2.c index c677884ac5e..ad4726bc71a 100644 --- a/gcc/testsuite/gcc.target/i386/sse2-mmx-paddsb-2.c +++ b/gcc/testsuite/gcc.target/i386/sse2-mmx-paddsb-2.c @@ -29,5 +29,5 @@ char baz() /* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$3," 1 } } */ /* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$127," 1 } } */ -/* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$-128," 1 } } */ +/* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$-?128," 1 } } */ /* { dg-final { scan-assembler-not "paddsb\[ \\t\]+%xmm\[0-9\]+" } } */ diff --git a/gcc/testsuite/gcc.target/i386/sse2-mmx-paddusb-2.c b/gcc/testsuite/gcc.target/i386/sse2-mmx-paddusb-2.c index b20891cf693..1d3bc8b5109 100644 --- a/gcc/testsuite/gcc.target/i386/sse2-mmx-paddusb-2.c +++ b/gcc/testsuite/gcc.target/i386/sse2-mmx-paddusb-2.c @@ -20,6 +20,6 @@ char bar() } /* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$3," 1 } } */ -/* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$-1," 1 } } */ +/* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$(?:255|-1)," 1 } } */ /* { dg-final { scan-assembler-not "paddusb\[ \\t\]+%xmm\[0-9\]+" } } */ diff --git a/gcc/testsuite/gcc.target/i386/sse2-mmx-psubsb-2.c b/gcc/testsuite/gcc.target/i386/sse2-mmx-psubsb-2.c index 4fc292079d1..68b57f2c971 100644 --- a/gcc/testsuite/gcc.target/i386/sse2-mmx-psubsb-2.c +++ b/gcc/testsuite/gcc.target/i386/sse2-mmx-psubsb-2.c @@ -28,6 +28,6 @@ char baz() } /* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$3," 1 } } */ -/* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$-128," 1 } } */ +/* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$-?128," 1 } } */ /* { dg-final { scan-assembler-times "movl\[ \\t\]+\\\$127," 1 } } */ /* { dg-final { scan-assembler-not "paddsb\[ \\t\]+%xmm\[0-9\]+" } } */
reply other threads:[~2021-10-08 8:35 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=20211008083506.35EB1385840E@sourceware.org \ --to=sayle@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).