From: "Kewen.Lin" <linkw@linux.ibm.com>
To: Ajit Agarwal <aagarwa1@linux.ibm.com>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
Peter Bergner <bergner@linux.ibm.com>,
Jeff Law <jeffreyalaw@gmail.com>,
Richard Biener <richard.guenther@gmail.com>,
David Edelsohn <dje.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v1] rs6000: Update powerpc test fold-vec-extract-int.p8.c
Date: Tue, 13 Jun 2023 16:28:31 +0800 [thread overview]
Message-ID: <4ccf01fb-a8e5-e70e-499e-5554eb53b5f5@linux.ibm.com> (raw)
In-Reply-To: <4b2a20b9-9f52-05b5-371c-e0734e0df6b7@linux.ibm.com>
Hi,
on 2023/5/19 15:40, Ajit Agarwal via Gcc-patches wrote:
> Hello All:
>
> Update powerpc tests for both le and be endian with extra removal of zero extension and sign extension.
> with default ree pass for rs6000 target.
Nice!
>
> Bootstrapped and regtested on powerpc64-linux-gnu.
>
> Thanks & Regards
> Ajit
>
> rs6000: Update powerpc test fold-vec-extract-int.p8.c
May be better to start with "testsuite:" or "testsuite, rs6000:".
>
> Update powerpc tests with extra zero_extend removal with default ree pass.
>
> 2023-05-19 Ajit Kumar Agarwal <aagarwa1@linux.ibm.com>
Since there is an upstream bug tracking this, could you add one PR
marker like:
PR testsuite/109880
OK for trunk with the PR marker added, thanks!
BR,
Kewen
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/powerpc/fold-vec-extract-int.p8.c: Update test.
> ---
> gcc/testsuite/gcc.target/powerpc/fold-vec-extract-int.p8.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gcc/testsuite/gcc.target/powerpc/fold-vec-extract-int.p8.c b/gcc/testsuite/gcc.target/powerpc/fold-vec-extract-int.p8.c
> index 75eaf25943b..f5f953320d8 100644
> --- a/gcc/testsuite/gcc.target/powerpc/fold-vec-extract-int.p8.c
> +++ b/gcc/testsuite/gcc.target/powerpc/fold-vec-extract-int.p8.c
> @@ -13,8 +13,8 @@
>
> /* { dg-final { scan-assembler-times {\mvspltw\M} 3 { target lp64 } } } */
> /* { dg-final { scan-assembler-times {\mmfvsrwz\M} 3 { target lp64 } } } */
> -/* { dg-final { scan-assembler-times {\mrldicl\M} 7 { target { le } } } } */
> -/* { dg-final { scan-assembler-times {\mrldicl\M} 4 { target { lp64 && be } } } } */
> +/* { dg-final { scan-assembler-times {\mrldicl\M} 5 { target { le } } } } */
> +/* { dg-final { scan-assembler-times {\mrldicl\M} 2 { target { lp64 && be } } } } */
> /* { dg-final { scan-assembler-times {\msubfic\M} 3 { target { le } } } } */
> /* { dg-final { scan-assembler-times {\msldi\M} 3 { target lp64 } } } */
> /* { dg-final { scan-assembler-times {\mmtvsrd\M} 3 { target lp64 } } } */
next prev parent reply other threads:[~2023-06-13 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 7:40 Ajit Agarwal
2023-06-13 8:28 ` Kewen.Lin [this message]
2023-06-13 8:39 ` [committed] " Ajit Agarwal
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=4ccf01fb-a8e5-e70e-499e-5554eb53b5f5@linux.ibm.com \
--to=linkw@linux.ibm.com \
--cc=aagarwa1@linux.ibm.com \
--cc=bergner@linux.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=richard.guenther@gmail.com \
--cc=segher@kernel.crashing.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).