From: Kito Cheng <kito.cheng@gmail.com>
To: 钟居哲 <juzhe.zhong@rivai.ai>
Cc: Robin Dapp <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
"Kito.cheng" <kito.cheng@sifive.com>,
palmer <palmer@dabbelt.com>, palmer <palmer@rivosinc.com>,
jeffreyalaw <jeffreyalaw@gmail.com>
Subject: Re: Re: [PATCH V2] RISC-V: Refactor the framework of RVV auto-vectorization
Date: Tue, 23 May 2023 17:56:51 +0800 [thread overview]
Message-ID: <CA+yXCZAQHxphD9d-5vFehCxZ+uGgE_byzTDCA-o3x5nbQ6D_=A@mail.gmail.com> (raw)
In-Reply-To: <8F969EE24FFFACD8+20230523174533405702164@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 873 bytes --]
Lgtm, we can always improve later, I am not intend to block things too :)
juzhe.zhong@rivai.ai <juzhe.zhong@rivai.ai> 於 2023年5月23日 週二 17:46 寫道：
> Oh， Thanks.
> Let's wait for Kito's final approved.
>
>
>
> juzhe.zhong@rivai.ai
>
> From: Robin Dapp
> Date: 2023-05-23 17:44
> To: juzhe.zhong; gcc-patches
> CC: rdapp.gcc; kito.cheng; kito.cheng; palmer; palmer; jeffreyalaw
> Subject: Re: [PATCH V2] RISC-V: Refactor the framework of RVV
> auto-vectorization
> Hi Juzhe,
>
> thanks, IMHO it's clearer with the changes now. There are still
> things that could be improved but it is surely an improvement over
> what we currently have. Therefore I'd vote to go ahead so we can
> continue with more expanders and changes.
>
> Still, we should be prepared for more refactoring changes in the future.
>
> Regards
> Robin
>
>
next prev parent reply other threads:[~2023-05-23 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 8:56 juzhe.zhong
2023-05-23 9:44 ` Robin Dapp
2023-05-23 9:45 ` juzhe.zhong
2023-05-23 9:56 ` Kito Cheng [this message]
2023-05-23 10:29 ` Li, Pan2
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='CA+yXCZAQHxphD9d-5vFehCxZ+uGgE_byzTDCA-o3x5nbQ6D_=A@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--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).