From: Richard Biener <richard.guenther@gmail.com>
To: Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
Cc: gcc Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <richard.sandiford@arm.com>
Subject: Re: [0/9] [middle-end] Add param to vec_perm_const hook to specify mode of input operand
Date: Thu, 19 May 2022 13:30:33 +0200 [thread overview]
Message-ID: <CAFiYyc09LVMo2r2ZkZMvUTFddXCFNvdAkM77ktVFp7iVwwV_AQ@mail.gmail.com> (raw)
In-Reply-To: <CAAgBjMktT4K=DE7ZR3URaESfh1rpnFobbXtAd_mEXVhJxM+vKg@mail.gmail.com>
On Wed, May 18, 2022 at 9:08 AM Prathamesh Kulkarni via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hi,
> The attached patch adds another parameter machine_mode op_mode to vec_perm_const
> hook to specify mode of input operands. The motivation for doing this
> is PR96463,
> where we create vec_perm_expr of the form:
> lhs = vec_perm_expr<rhs, mask>
> where lhs and rhs have different vector types but same element type
> (lhs is SVE and rhs is corresponding advsimd vector).
>
> It seems the following targets were affected: aarch64, i386, arm, ia64,
> mips, rs6000, s390, sparc, gcn.
>
> Bootstrapped+tested on x86_64-linux-gnu, aarch64-linux-gnu.
> For other targets, I did make all-gcc stage1, which seems to build OK.
So it would also allow to express extract even/odd and interleave operations
with a VEC_PERM. The interleave currently has the issue that we have
to artificially widen the inputs with "dont-care" elements. The lo/high
variants can already do with a bitfield-ref or vector-of-vector CTOR.
Richard.
>
> Thanks,
> Prathamesh
prev parent reply other threads:[~2022-05-19 11:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-18 7:06 Prathamesh Kulkarni
2022-05-18 9:38 ` Andre Vieira (lists)
2022-05-18 11:57 ` Richard Sandiford
2022-05-23 8:47 ` Prathamesh Kulkarni
2022-05-23 12:44 ` Richard Sandiford
2022-05-24 9:02 ` Prathamesh Kulkarni
2022-05-24 9:20 ` Richard Sandiford
2022-05-24 19:21 ` Prathamesh Kulkarni
2022-05-25 12:57 ` Richard Biener
2022-05-25 19:02 ` Prathamesh Kulkarni
2022-05-25 19:07 ` Richard Biener
2022-05-25 20:23 ` Prathamesh Kulkarni
2022-05-27 13:40 ` Richard Biener
2022-05-30 8:15 ` Richard Sandiford
2022-05-19 11:30 ` Richard Biener [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=CAFiYyc09LVMo2r2ZkZMvUTFddXCFNvdAkM77ktVFp7iVwwV_AQ@mail.gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=prathamesh.kulkarni@linaro.org \
--cc=richard.sandiford@arm.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).