From: Jeff Law <jeffreyalaw@gmail.com>
To: "Kito Cheng" <kito.cheng@sifive.com>, 钟居哲 <juzhe.zhong@rivai.ai>
Cc: "rdapp.gcc" <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"kito.cheng" <kito.cheng@gmail.com>, palmer <palmer@dabbelt.com>,
palmer <palmer@rivosinc.com>
Subject: Re: [PATCH] RISC-V: Enhance RVV VLA SLP auto-vectorization with decompress operation
Date: Mon, 12 Jun 2023 08:56:04 -0600 [thread overview]
Message-ID: <9097a0b4-b8ac-a548-024d-3030948ef861@gmail.com> (raw)
In-Reply-To: <CALLt3TjMX88X9V9siPFXC+7oMJgz6kBcE6C_AnQWDTeyAhsT2g@mail.gmail.com>
On 6/12/23 08:54, Kito Cheng wrote:
> I didn't take a close review yet, (and I suspect I can't find time
> before I start my vacation :P), but I am thinking we may adding
> selftests for expand_const_vector in *future*, again, not blocker for
> this patch :)
I'll take this one. Go enjoy your vacation!
jeff
prev parent reply other threads:[~2023-06-12 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 13:29 juzhe.zhong
2023-06-12 14:43 ` Robin Dapp
2023-06-12 14:51 ` 钟居哲
2023-06-12 14:54 ` Kito Cheng
2023-06-12 14:56 ` Jeff Law [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=9097a0b4-b8ac-a548-024d-3030948ef861@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).