From: Kito Cheng <kito.cheng@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: 钟居哲 <juzhe.zhong@rivai.ai>, gcc-patches <gcc-patches@gcc.gnu.org>,
palmer <palmer@dabbelt.com>
Subject: Re: [PATCH] RISC-V: Add testcases for VSETVL PASS
Date: Mon, 19 Dec 2022 11:22:16 +0800 [thread overview]
Message-ID: <CA+yXCZDOUHmTCkxhQeK1F82C6U6nSzNQB8isJc=ui5MGxS5J2g@mail.gmail.com> (raw)
In-Reply-To: <31305c93-d716-f8f2-a061-ccecc62f95b2@gmail.com>
Hi Jeff:
> Ah, I should have looked at those regexps closer. Understood about the
> checking for hoisting the vsetvl. Though it makes me wonder if we'd be
> better off dumping information out of the vsetvl pass.
I've discussed adding an extra verify pass and a kind of rating
mechnish to vsetvli pass with Ju-Zhe,
so that we don't need to do such asm scan, which is relatively fragile
to broken.
And we'll implement that in the next few weeks :)
Thanks
next prev parent reply other threads:[~2022-12-19 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 8:09 juzhe.zhong
2022-12-16 20:07 ` Jeff Law
2022-12-17 1:31 ` 钟居哲
2022-12-17 1:42 ` Jeff Law
2022-12-19 3:22 ` Kito Cheng [this message]
2022-12-26 9:20 ` Andreas Schwab
2022-12-26 9:28 ` 钟居哲
2022-12-27 15:04 ` Jeff Law
2022-12-27 15:12 ` Kito Cheng
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+yXCZDOUHmTCkxhQeK1F82C6U6nSzNQB8isJc=ui5MGxS5J2g@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--cc=palmer@dabbelt.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).