From: "juzhe.zhong@rivai.ai" <juzhe.zhong@rivai.ai>
To: "Robin Dapp" <rdapp.gcc@gmail.com>, kito.cheng <kito.cheng@gmail.com>
Cc: "Robin Dapp" <rdapp.gcc@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
Kito.cheng <kito.cheng@sifive.com>
Subject: Re: Re: [PATCH V4] RISC-V: Enable vec_int testsuite for RVV VLA vectorization
Date: Tue, 29 Aug 2023 08:40:16 +0800 [thread overview]
Message-ID: <CEFE86E9929ED6A5+2023082908401567291437@rivai.ai> (raw)
In-Reply-To: <07474492-1fa9-db00-5b3f-0cd9b63e6c34@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 796 bytes --]
>> Juzhe mentioned he doesn't want to commit this before
>> all/most bugs are addresses anyway, right?
Yes.
juzhe.zhong@rivai.ai
From: Robin Dapp
Date: 2023-08-28 22:27
To: Kito Cheng; Juzhe-Zhong
CC: rdapp.gcc; gcc-patches; kito.cheng
Subject: Re: [PATCH V4] RISC-V: Enable vec_int testsuite for RVV VLA vectorization
> LGTM from my side, but I would like to wait Robin is ok too
In principle I'm OK with it as well, realizing we will still need to fine-tune
a lot here anyway. For now, IMHO it's good to have some additional test coverage
in the vector space but we should not expect every test to be correct/a good match
for everything we do yet. Juzhe mentioned he doesn't want to commit this before
all/most bugs are addresses anyway, right?
Regards
Robin
prev parent reply other threads:[~2023-08-29 0:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 11:42 Juzhe-Zhong
2023-08-28 14:18 ` Kito Cheng
2023-08-28 14:27 ` Robin Dapp
2023-08-28 18:49 ` Jeff Law
2023-08-29 0:40 ` juzhe.zhong [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=CEFE86E9929ED6A5+2023082908401567291437@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.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).