From: Lehua Ding <lehua.ding@rivai.ai>
To: Robin Dapp <rdapp.gcc@gmail.com>,
Juzhe-Zhong <juzhe.zhong@rivai.ai>,
gcc-patches@gcc.gnu.org
Cc: kito.cheng@gmail.com, kito.cheng@sifive.com, jeffreyalaw@gmail.com
Subject: Re: [PATCH V2] RISC-V: Fix failed hoist in LICM of vmv.v.x instruction
Date: Fri, 20 Oct 2023 11:59:32 +0800 [thread overview]
Message-ID: <104E578C3CB48C31+00f21420-ab12-46f6-a397-617dbf7c5783@rivai.ai> (raw)
In-Reply-To: <f8df4ca0-d509-4096-bdac-a28d5032c124@gmail.com>
Committed after the commited of the vsetvl pass refactor patch, thanks
Robin.
On 2023/10/19 16:43, Robin Dapp wrote:
> Hi Juzhe,
>
> as discussed off-list this approach generally makes sense to me so
> the patch LGTM once the vsetvl rework is upstream and settled.
>
> Independently, we still need to understand why the more complex
> broadcast pattern is not hoisted out of the loop.
>
> Regards
> Robin
--
Best,
Lehua (RiVAI)
lehua.ding@rivai.ai
prev parent reply other threads:[~2023-10-20 3:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 10:25 Juzhe-Zhong
2023-10-18 10:51 ` juzhe.zhong
2023-10-19 8:43 ` Robin Dapp
2023-10-19 8:53 ` 钟居哲
2023-10-20 3:59 ` Lehua Ding [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=104E578C3CB48C31+00f21420-ab12-46f6-a397-617dbf7c5783@rivai.ai \
--to=lehua.ding@rivai.ai \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=juzhe.zhong@rivai.ai \
--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).