From: David Edelsohn <dje.gcc@gmail.com>
To: Bill Schmidt <wschmidt@linux.ibm.com>,
Michael Meissner <meissner@linux.ibm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Segher Boessenkool <segher@kernel.crashing.org>,
Peter Bergner <bergner@linux.ibm.com>,
Will Schmidt <will_schmidt@vnet.ibm.com>
Subject: Re: [PATCH] PR 102935, Fix pr101384-1.c code generation test.
Date: Tue, 11 Jan 2022 13:23:00 -0500 [thread overview]
Message-ID: <CAGWvnynCzC-SxweqTXF48jOo_Tefv2wf3vKZ1+Z7Wi-A+Lp05g@mail.gmail.com> (raw)
In-Reply-To: <91eb3605-0292-5573-ce09-fb6c4d846ef8@linux.ibm.com>
On Tue, Jan 11, 2022 at 12:06 PM Bill Schmidt <wschmidt@linux.ibm.com> wrote:
>
> Hi Mike,
>
> This looks fine to me. Maintainers?
Okay.
Thanks, David
>
> Thanks,
> Bill
>
> On 1/7/22 6:33 PM, Michael Meissner wrote:
> > Fix pr101384-1.c code generation test.
> >
> > Add support for the compiler using XXSPLTIB reg,255 to load all 1's into a
> > register on power9 and above instead of using VSPLTI{B,H,W} reg,-1.
> >
> > gcc/testsuite/
> > 2022-01-07 Michael Meissner <meissner@the-meissners.org>
> >
> > PR testsuite/102935
> > * gcc.target/powerpc/pr101384-1.c: Update insn regexp for power9
> > and power10.
> > ---
> > gcc/testsuite/gcc.target/powerpc/pr101384-1.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/gcc/testsuite/gcc.target/powerpc/pr101384-1.c b/gcc/testsuite/gcc.target/powerpc/pr101384-1.c
> > index 627d7d76721..41cf84bf8bc 100644
> > --- a/gcc/testsuite/gcc.target/powerpc/pr101384-1.c
> > +++ b/gcc/testsuite/gcc.target/powerpc/pr101384-1.c
> > @@ -2,7 +2,7 @@
> > /* { dg-do compile { target le } } */
> > /* { dg-options "-O2 -maltivec" } */
> > /* { dg-require-effective-target powerpc_altivec_ok } */
> > -/* { dg-final { scan-assembler-times {\mvspltis[whb] [^\n\r]*,-1\M} 9 } } */
> > +/* { dg-final { scan-assembler-times {\mvspltis[whb] [^\n\r]*,-1\M|\mxxspltib[^\n\r]*,255\M} 9 } } */
> > /* { dg-final { scan-assembler-times {\mvslw\M} 3 } } */
> > /* { dg-final { scan-assembler-times {\mvslh\M} 3 } } */
> > /* { dg-final { scan-assembler-times {\mvslb\M} 3 } } */
prev parent reply other threads:[~2022-01-11 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 0:33 Michael Meissner
2022-01-11 17:06 ` Bill Schmidt
2022-01-11 18:23 ` David Edelsohn [this message]
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=CAGWvnynCzC-SxweqTXF48jOo_Tefv2wf3vKZ1+Z7Wi-A+Lp05g@mail.gmail.com \
--to=dje.gcc@gmail.com \
--cc=bergner@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=meissner@linux.ibm.com \
--cc=segher@kernel.crashing.org \
--cc=will_schmidt@vnet.ibm.com \
--cc=wschmidt@linux.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).