From: "Li, Pan2" <pan2.li@intel.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "kito.cheng@gmail.com" <kito.cheng@gmail.com>,
"kito.cheng@sifive.com" <kito.cheng@sifive.com>,
"palmer@dabbelt.com" <palmer@dabbelt.com>,
"palmer@rivosinc.com" <palmer@rivosinc.com>,
"rdapp.gcc@gmail.com" <rdapp.gcc@gmail.com>
Subject: RE: [PATCH V2] RISC-V: Support RVV permutation auto-vectorization
Date: Fri, 2 Jun 2023 01:03:32 +0000 [thread overview]
Message-ID: <MW5PR11MB5908879BDB94DF0204082612A94EA@MW5PR11MB5908.namprd11.prod.outlook.com> (raw)
In-Reply-To: <b79ec934-540f-6ca8-d13f-e854a1632afa@gmail.com>
Committed, thanks Jeff.
Pan
-----Original Message-----
From: Gcc-patches <gcc-patches-bounces+pan2.li=intel.com@gcc.gnu.org> On Behalf Of Jeff Law via Gcc-patches
Sent: Friday, June 2, 2023 2:49 AM
To: juzhe.zhong@rivai.ai; gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com; kito.cheng@sifive.com; palmer@dabbelt.com; palmer@rivosinc.com; rdapp.gcc@gmail.com
Subject: Re: [PATCH V2] RISC-V: Support RVV permutation auto-vectorization
On 5/31/23 20:36, juzhe.zhong@rivai.ai wrote:
> From: Juzhe-Zhong <juzhe.zhong@rivai.ai>
>
> This patch supports vector permutation for VLS only by vec_perm pattern.
> We will support TARGET_VECTORIZE_VEC_PERM_CONST to support VLA
> permutation in the future.
>
> Fixed following comments from Robin.
> Ok for trunk?
>
> gcc/ChangeLog:
>
> * config/riscv/autovec.md (vec_perm<mode>): New pattern.
> * config/riscv/predicates.md (vector_perm_operand): New predicate.
> * config/riscv/riscv-protos.h (enum insn_type): New enum.
> (expand_vec_perm): New function.
> * config/riscv/riscv-v.cc (const_vec_all_in_range_p): Ditto.
> (gen_const_vector_dup): Ditto.
> (emit_vlmax_gather_insn): Ditto.
> (emit_vlmax_masked_gather_mu_insn): Ditto.
> (expand_vec_perm): Ditto.
OK.
jeff
prev parent reply other threads:[~2023-06-02 1:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 2:36 juzhe.zhong
2023-06-01 18:48 ` Jeff Law
2023-06-02 1:03 ` Li, Pan2 [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=MW5PR11MB5908879BDB94DF0204082612A94EA@MW5PR11MB5908.namprd11.prod.outlook.com \
--to=pan2.li@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.com \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=rdapp.gcc@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).