From: Robin Dapp <rdapp.gcc@gmail.com>
To: Kito Cheng <kito.cheng@gmail.com>, Juzhe-Zhong <juzhe.zhong@rivai.ai>
Cc: rdapp.gcc@gmail.com, gcc-patches@gcc.gnu.org, kito.cheng@sifive.com
Subject: Re: [PATCH V4] RISC-V: Enable vec_int testsuite for RVV VLA vectorization
Date: Mon, 28 Aug 2023 16:27:58 +0200 [thread overview]
Message-ID: <07474492-1fa9-db00-5b3f-0cd9b63e6c34@gmail.com> (raw)
In-Reply-To: <CA+yXCZDJZ9G1a6L0Z+2kFgK171UmOpSRykNmTd9TiuhbqesvrQ@mail.gmail.com>
> 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
next prev parent reply other threads:[~2023-08-28 14:28 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 [this message]
2023-08-28 18:49 ` Jeff Law
2023-08-29 0: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=07474492-1fa9-db00-5b3f-0cd9b63e6c34@gmail.com \
--to=rdapp.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=juzhe.zhong@rivai.ai \
--cc=kito.cheng@gmail.com \
--cc=kito.cheng@sifive.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).