From: Jakub Jelinek <jakub@redhat.com>
To: Tamar Christina <Tamar.Christina@arm.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
Hongyu Wang <wwwhhhyyy333@gmail.com>,
Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>,
Richard Sandiford <Richard.Sandiford@arm.com>,
Hongyu Wang <hongyu.wang@intel.com>,
"hongtao.liu@intel.com" <hongtao.liu@intel.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Optimize VEC_PERM_EXPR with same permutation index and operation [PR98167]
Date: Wed, 16 Nov 2022 16:41:01 +0100 [thread overview]
Message-ID: <Y3UEjb+7at2XWbaK@tucnak> (raw)
In-Reply-To: <VI1PR08MB53250E27431C197DDA345003FF079@VI1PR08MB5325.eurprd08.prod.outlook.com>
On Wed, Nov 16, 2022 at 03:40:02PM +0000, Tamar Christina wrote:
> > Even:
> >
> > --- gcc/match.pd.jj 2022-11-15 07:56:05.240348804 +0100
> > +++ gcc/match.pd 2022-11-16 16:35:34.854080956 +0100
> > @@ -8259,7 +8259,7 @@ and,
> > (simplify
> > (op (vec_perm @0 @0 @2) (vec_perm @1 @1 @2))
> > (if (VECTOR_INTEGER_TYPE_P (type))
> > - (vec_perm (op @0 @1) (op @0 @1) @2))))
> > + (vec_perm (op@3 @0 @1) @3 @2))))
> >
> > /* Similar for float arithmetic when permutation constant covers
> > all vector elements. */
> > @@ -8298,4 +8298,4 @@ and,
> > }
> > }
> > (if (full_perm_p)
> > - (vec_perm (op @0 @1) (op @0 @1) @2))))))
> > + (vec_perm (op@3 @0 @1) @3 @2))))))
> >
> > From quick look at the dumps, it seems to work fine.
> >
> > Jakub
>
> Yes that's the patch I'm currently reg-testing 😊
Great ;)
Jakub
next prev parent reply other threads:[~2022-11-16 15:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 0:04 Hongyu Wang
2022-11-04 6:43 ` Prathamesh Kulkarni
2022-11-08 14:37 ` Richard Biener
2022-11-10 2:22 ` Hongyu Wang
2022-11-10 8:56 ` Richard Biener
2022-11-10 14:27 ` Hongyu Wang
2022-11-14 14:53 ` Richard Biener
2022-11-16 15:25 ` Tamar Christina
2022-11-16 15:29 ` Richard Biener
2022-11-16 15:30 ` Richard Biener
2022-11-16 15:34 ` Tamar Christina
2022-11-16 15:37 ` Jakub Jelinek
2022-11-16 15:40 ` Tamar Christina
2022-11-16 15:41 ` Jakub Jelinek [this message]
2022-11-16 19:21 ` Marc Glisse
2022-11-17 6:05 ` Hongyu Wang
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=Y3UEjb+7at2XWbaK@tucnak \
--to=jakub@redhat.com \
--cc=Richard.Sandiford@arm.com \
--cc=Tamar.Christina@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hongtao.liu@intel.com \
--cc=hongyu.wang@intel.com \
--cc=prathamesh.kulkarni@linaro.org \
--cc=richard.guenther@gmail.com \
--cc=wwwhhhyyy333@gmail.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).