From: <juzhe.zhong@rivai.ai>
To: "Jeff Law" <jeffreyalaw@gmail.com>, rguenther <rguenther@suse.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
kito.cheng <kito.cheng@gmail.com>,
richard.sandiford <richard.sandiford@arm.com>,
apinski <apinski@marvell.com>
Subject: Re: Re: [PATCH] CPROP: Allow cprop optimization when the function has a single block
Date: Thu, 2 Feb 2023 22:43:28 +0800 [thread overview]
Message-ID: <894D5A99B5C3944F+2023020222432718712219@rivai.ai> (raw)
In-Reply-To: <b0b43224-f10a-b522-6c8d-9edb8f493b68@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
We set VL/VTYPE these 2 implicit global status denpency register as fixed reg.
Then CSE can do the optimization now.
>> Yea. I'm wondering about when the right place to introduce these
>>dependencies might be. I'm still a few months out from worrying about
>>RVV, but it's not too far away.
You don't need to worry about RVV. I can promise you that RVV support in GCC will be solid and
optimal. You can just try. For example, try VSETVL PASS, this PASS implemented in GCC is much better
than LLVM. I have include so many fancy optimizations there.
juzhe.zhong@rivai.ai
From: Jeff Law
Date: 2023-02-02 22:36
To: juzhe.zhong@rivai.ai; rguenther
CC: gcc-patches; kito.cheng; richard.sandiford; apinski
Subject: Re: [PATCH] CPROP: Allow cprop optimization when the function has a single block
On 2/2/23 05:35, juzhe.zhong@rivai.ai wrote:
> Thank you so much. Kito helped me fix it already.
> RVV instruction patterns can have CSE optimizations now.
What was the issue?
jeff
next prev parent reply other threads:[~2023-02-02 14:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 12:24 juzhe.zhong
2023-02-01 12:40 ` Richard Biener
2023-02-01 12:47 ` juzhe.zhong
2023-02-01 12:51 ` Richard Biener
2023-02-01 12:56 ` juzhe.zhong
[not found] ` <0CEDD257-703F-4ED3-B927-C21279557CE6@gmail.com>
2023-02-02 1:49 ` juzhe.zhong
2023-02-02 12:26 ` Richard Biener
2023-02-02 12:35 ` juzhe.zhong
2023-02-02 14:36 ` Jeff Law
2023-02-02 14:43 ` juzhe.zhong [this message]
2023-02-02 15:18 ` Kito Cheng
2023-02-02 14:36 ` Jeff Law
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=894D5A99B5C3944F+2023020222432718712219@rivai.ai \
--to=juzhe.zhong@rivai.ai \
--cc=apinski@marvell.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=kito.cheng@gmail.com \
--cc=rguenther@suse.de \
--cc=richard.sandiford@arm.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).