From: Jeff Law <jeffreyalaw@gmail.com>
To: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>,
gcc-patches <gcc-patches@gcc.gnu.org>
Cc: "kito.cheng" <kito.cheng@gmail.com>,
"Kito.cheng" <kito.cheng@sifive.com>, palmer <palmer@dabbelt.com>,
palmer <palmer@rivosinc.com>, Robin Dapp <rdapp.gcc@gmail.com>,
"pan2.li" <pan2.li@intel.com>
Subject: Re: [PATCH V2] RISC-V: Support RVV VLA SLP auto-vectorization
Date: Tue, 13 Jun 2023 08:06:51 -0600 [thread overview]
Message-ID: <c264d468-ff4d-bd1f-a3ad-94bc10415a2b@gmail.com> (raw)
In-Reply-To: <B94725CABFEB1972+2023061310271005805912@rivai.ai>
On 6/12/23 20:27, juzhe.zhong@rivai.ai wrote:
> Ok.
> https://gcc.gnu.org/pipermail/gcc-patches/2023-June/thread.html
> <https://gcc.gnu.org/pipermail/gcc-patches/2023-June/thread.html>
> I have add comments as you suggested.
Thanks. With those changes I think the main patch here (RVV VLA SLP
auto-vectorization) is good to go.
jeff
prev parent reply other threads:[~2023-06-13 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 3:19 juzhe.zhong
2023-06-12 23:21 ` Jeff Law
2023-06-13 2:27 ` juzhe.zhong
2023-06-13 14:06 ` 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=c264d468-ff4d-bd1f-a3ad-94bc10415a2b@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=pan2.li@intel.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).