From: Kito Cheng <kito.cheng@gmail.com>
To: juzhe.zhong@rivai.ai
Cc: gcc-patches@gcc.gnu.org, palmer@dabbelt.com
Subject: Re: [PATCH] RISC-V: Refine codes in backward fusion
Date: Fri, 27 Jan 2023 03:15:23 +0800 [thread overview]
Message-ID: <CA+yXCZBT7OfRe=CFY2yE9WGffvMCD87Yj+ZjNV8Y9bt4VtnUwQ@mail.gmail.com> (raw)
In-Reply-To: <20230109224726.148263-1-juzhe.zhong@rivai.ai>
[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]
committed, thanks.
On Tue, Jan 10, 2023 at 6:47 AM <juzhe.zhong@rivai.ai> wrote:
> From: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
>
> This NFC patch is preparing for the following patches.
> gcc/ChangeLog:
>
> * config/riscv/riscv-vsetvl.cc
> (pass_vsetvl::backward_demand_fusion): Refine codes.
>
> ---
> gcc/config/riscv/riscv-vsetvl.cc | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/gcc/config/riscv/riscv-vsetvl.cc
> b/gcc/config/riscv/riscv-vsetvl.cc
> index 18c6f437db6..0ca1c51d121 100644
> --- a/gcc/config/riscv/riscv-vsetvl.cc
> +++ b/gcc/config/riscv/riscv-vsetvl.cc
> @@ -2010,15 +2010,16 @@ pass_vsetvl::backward_demand_fusion (void)
> for (const bb_info *bb : crtl->ssa->reverse_bbs ())
> {
> basic_block cfg_bb = bb->cfg_bb ();
> - const auto &prop
> - = m_vector_manager->vector_block_infos[cfg_bb->index].local_dem;
> + const auto &curr_block_info
> + = m_vector_manager->vector_block_infos[cfg_bb->index];
> + const auto &prop = curr_block_info.local_dem;
>
> /* If there is nothing to propagate, just skip it. */
> if (!prop.valid_or_dirty_p ())
> continue;
>
> - if (!backward_propagate_worthwhile_p (
> - cfg_bb, m_vector_manager->vector_block_infos[cfg_bb->index]))
> + if (!backward_propagate_worthwhile_p (cfg_bb, curr_block_info))
> + continue;
> continue;
>
> edge e;
> --
> 2.36.1
>
>
prev parent reply other threads:[~2023-01-26 19:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 22:47 juzhe.zhong
2023-01-26 19:15 ` 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+yXCZBT7OfRe=CFY2yE9WGffvMCD87Yj+ZjNV8Y9bt4VtnUwQ@mail.gmail.com' \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--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).