From: Jeff Law <jeffreyalaw@gmail.com>
To: Robin Dapp <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Kito Cheng <kito.cheng@gmail.com>,
"Kito.cheng" <Kito.cheng@sifive.com>, palmer <palmer@dabbelt.com>,
"juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
Michael Collison <collison@rivosinc.com>
Subject: Re: [PATCH] riscv: Allow vector constants in riscv_const_insns.
Date: Fri, 28 Apr 2023 14:34:39 -0600 [thread overview]
Message-ID: <6a8dbe8d-89b2-e5c8-91bb-53f0baca2ae2@gmail.com> (raw)
In-Reply-To: <46ca12b2-8ac6-030e-92dc-6b71ab2d4ee8@gmail.com>
On 4/28/23 10:10, Robin Dapp wrote:
> Hi,
>
> I figured I'm going to start sending some patches that build on top
> of the upcoming RISC-V autovectorization. This one is obviously
> not supposed to be installed before the basic support lands but
> it's small enough that it shouldn't hurt to send it now.
>
> This patch allows vector constants in riscv_const_insns in order
> for them to be properly recognized as immediate operands such that
> we can emit vmv.v.i instructions via autovec.
>
> Bootstrapped and regtested on riscv32gcv and riscv64gcv.
>
> Regards
> Robin
>
> --
>
> gcc/ChangeLog:
>
> * config/riscv/riscv.cc (riscv_const_insns): Add permissible
> vector constants.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/riscv/rvv/autovec/vmv-imm.c: New test.
OK for the trunk once the basic bits are in.
jeff
next prev parent reply other threads:[~2023-04-28 20:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 16:10 Robin Dapp
2023-04-28 20:34 ` Jeff Law [this message]
2023-05-04 5:07 ` juzhe.zhong
2023-05-06 20:11 ` Jeff Law
2023-05-07 0:09 ` 钟居哲
2023-05-11 12:47 ` [PATCH v2] RISC-V: " Robin Dapp
2023-05-11 14:15 ` Kito Cheng
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=6a8dbe8d-89b2-e5c8-91bb-53f0baca2ae2@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=Kito.cheng@sifive.com \
--cc=collison@rivosinc.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=palmer@dabbelt.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).