From: Jeff Law <jeffreyalaw@gmail.com>
To: "juzhe.zhong" <juzhe.zhong@rivai.ai>
Cc: Kito Cheng <kito.cheng@gmail.com>,
Richard Biener <richard.guenther@gmail.com>,
Robin Dapp <rdapp.gcc@gmail.com>,
"Kito.cheng" <kito.cheng@sifive.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@dabbelt.com>, "pan2.li" <pan2.li@intel.com>
Subject: Re: [PATCH] RISC-V: Basic VLS code gen for RISC-V
Date: Tue, 13 Jun 2023 10:10:09 -0600 [thread overview]
Message-ID: <12849716-caa0-049f-1ad4-cb842653014d@gmail.com> (raw)
In-Reply-To: <529320C359BE5467+690CDE73-D54E-48E2-81C4-B742060D7F28@rivai.ai>
On 6/12/23 17:39, juzhe.zhong wrote:
> I take this work which is very important for VLA SLP too. I will
> support VLS after I finish VLA SLP.
OK. I think I'll mark Kito's patch as dropped and we'll wait for your
implementation in this space.
jeff
next prev parent reply other threads:[~2023-06-13 16:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 6:06 Kito Cheng
2023-05-30 6:32 ` juzhe.zhong
2023-05-30 6:51 ` Kito Cheng
2023-05-30 6:59 ` juzhe.zhong
2023-05-30 7:13 ` Richard Biener
2023-05-30 7:45 ` juzhe.zhong
2023-05-30 9:05 ` Robin Dapp
2023-05-30 9:11 ` Kito Cheng
2023-05-30 9:16 ` Kito Cheng
2023-05-30 9:16 ` juzhe.zhong
2023-05-30 9:29 ` Richard Biener
2023-05-30 9:37 ` juzhe.zhong
2023-05-30 9:44 ` juzhe.zhong
2023-05-30 15:45 ` Kito Cheng
2023-05-30 23:19 ` 钟居哲
[not found] ` <DC99791C4B2B4D40+106F137E-2B0D-4732-A7C5-8EE0242F9F5A@rivai.ai>
2023-06-12 23:34 ` Jeff Law
[not found] ` <529320C359BE5467+690CDE73-D54E-48E2-81C4-B742060D7F28@rivai.ai>
2023-06-13 16:10 ` Jeff Law [this message]
2023-05-30 7:27 ` Robin Dapp
2023-05-30 7:40 ` juzhe.zhong
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=12849716-caa0-049f-1ad4-cb842653014d@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=pan2.li@intel.com \
--cc=rdapp.gcc@gmail.com \
--cc=richard.guenther@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).