From: Will Schmidt <will_schmidt@vnet.ibm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH, rs6000] Fix PR86592 (p8-vec-xl-xst-v2.c)
Date: Tue, 18 Sep 2018 20:39:00 -0000 [thread overview]
Message-ID: <1537302865.19375.21.camel@brimstone.rchland.ibm.com> (raw)
Hi,
The expected codegen for this testcase with target {le} and
option -mcpu=power8 is lxvd2x and stxvd2x. It was initially
committed with contents as seen on builds for P7, which was
incorrect. Update as is appropriate.
[testsuite]
2018-09-18 Will Schmidt <will_schmidt@vnet.ibm.com>
PR testsuite/86592
* p8-vec-xl-xst-v2.c: Add and update expected codegen.
diff --git a/gcc/testsuite/gcc.target/powerpc/p8-vec-xl-xst-v2.c b/gcc/testsuite/gcc.target/powerpc/p8-vec-xl-xst-v2.c
index cc68ceb..6f48d72 100644
--- a/gcc/testsuite/gcc.target/powerpc/p8-vec-xl-xst-v2.c
+++ b/gcc/testsuite/gcc.target/powerpc/p8-vec-xl-xst-v2.c
@@ -57,8 +57,7 @@ void
bartle (vector unsigned short x, unsigned short * address)
{
vec_xst (x, 0, address);
}
-/* { dg-final { scan-assembler-times "lvx" 4 } } */
-/* { dg-final { scan-assembler-times "stvx" 4 } } */
-/* { dg-final { scan-assembler-times "xxpermdi" 0 } } */
+/* { dg-final { scan-assembler-times {\mlxvd2x\M} 4 } } */
+/* { dg-final { scan-assembler-times {\mstxvd2x\M} 4 } } */
next reply other threads:[~2018-09-18 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 20:39 Will Schmidt [this message]
2018-09-21 15:04 ` Segher Boessenkool
-- strict thread matches above, loose matches on Subject: below --
2018-09-18 20:31 [PATCH, rs6000] Fix PR86952 (p8-vec-xl-xst-v2.c) Will Schmidt
2018-09-18 20:34 ` [PATCH, rs6000] Fix PR86592 (p8-vec-xl-xst-v2.c) Will Schmidt
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=1537302865.19375.21.camel@brimstone.rchland.ibm.com \
--to=will_schmidt@vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
--cc=wschmidt@linux.vnet.ibm.com \
/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).