From: 钟居哲 <juzhe.zhong@rivai.ai>
To: "Jeff Law" <jeffreyalaw@gmail.com>,
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>, rdapp.gcc <rdapp.gcc@gmail.com>,
pan2.li <pan2.li@intel.com>
Subject: Re: Re: [PATCH V2] RISC-V: Rework Phase 5 && Phase 6 of VSETVL PASS
Date: Sat, 10 Jun 2023 06:52:15 +0800 [thread overview]
Message-ID: <CFCCA0FABB7CE6F8+202306100652148417041@rivai.ai> (raw)
In-Reply-To: <79d48828-0dad-de54-5388-1e2651e3b739@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
Ok. Thanks.
juzhe.zhong@rivai.ai
From: Jeff Law
Date: 2023-06-09 23:09
To: 钟居哲; gcc-patches
CC: kito.cheng; kito.cheng; palmer; palmer; rdapp.gcc; pan2.li
Subject: Re: [PATCH V2] RISC-V: Rework Phase 5 && Phase 6 of VSETVL PASS
On 6/9/23 08:58, 钟居哲 wrote:
>>> I'd probably adjust the name as well. There's an important exception to
>>> returning the first vsetvl -- you stop the search if you encounter a
>>> user RVV instruction.
>
> Could you give me a function name of this?
> like:
> get_first_vsetvl_prior_all_rvv_insns
> is it ok? But I think the name is too long.
get_first_vsetvl_before_rvv_insns? It's a bit smaller and I think
captures the key exception -- does that work for you?
Jeff
next prev parent reply other threads:[~2023-06-09 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 10:41 juzhe.zhong
2023-06-09 10:45 ` Kito Cheng
2023-06-09 10:49 ` juzhe.zhong
2023-06-09 14:33 ` Jeff Law
2023-06-09 14:46 ` 钟居哲
2023-06-09 14:58 ` 钟居哲
2023-06-09 15:09 ` Jeff Law
2023-06-09 22:52 ` 钟居哲 [this message]
2023-06-12 19:02 ` Richard Sandiford
2023-06-16 10:55 ` Andreas Schwab
2023-06-16 11:39 ` 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=CFCCA0FABB7CE6F8+202306100652148417041@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--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).