From: Kito Cheng <kito.cheng@gmail.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: juzhe.zhong@rivai.ai, gcc-patches@gcc.gnu.org, palmer@dabbelt.com
Subject: Re: [PATCH] RISC-V: Change VSETVL PASS always call split_all_insns
Date: Fri, 27 Jan 2023 17:36:30 +0800 [thread overview]
Message-ID: <CA+yXCZCySmmgq8P7hsVQT0GMsd1WN3V2Xsz2tTpS=rTAnS67FA@mail.gmail.com> (raw)
In-Reply-To: <7bd8c0ff-754f-5224-795e-ac101bbf1e03@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 684 bytes --]
committed, thanks
On Mon, Jan 23, 2023 at 3:39 AM Jeff Law via Gcc-patches <
gcc-patches@gcc.gnu.org> wrote:
>
>
> On 1/17/23 19:50, juzhe.zhong@rivai.ai wrote:
> > From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
> >
> > Since LCM will destroy CFG, we are going to reorder the location of
> VSETVL PASS
> > at least before bbro (block-reorder PASS) which is before split3 PASS.
> We need
> > to call it in VSETVL PASS to get final RVV instructions patterns.
> Just for the record. LCM does not destroy the CFG, it just splits
> critical edges.
>
> >
> > gcc/ChangeLog:
> >
> > * config/riscv/riscv-vsetvl.cc (pass_vsetvl::execute): Always
> call split_all_insns.
> OK.
> jeff
>
prev parent reply other threads:[~2023-01-27 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 2:50 juzhe.zhong
2023-01-22 19:39 ` Jeff Law
2023-01-27 9:36 ` Kito Cheng [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='CA+yXCZCySmmgq8P7hsVQT0GMsd1WN3V2Xsz2tTpS=rTAnS67FA@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).