public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Kito Cheng <kito@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5412] RISC-V: Refine codes in backward fusion [NFC]
Date: Thu, 26 Jan 2023 19:12:41 +0000 (GMT)	[thread overview]
Message-ID: <20230126191241.858FD3858C62@sourceware.org> (raw)

https://gcc.gnu.org/g:b9b251b7b95c78b485022802908970c598d9f6e1

commit r13-5412-gb9b251b7b95c78b485022802908970c598d9f6e1
Author: Ju-Zhe Zhong <juzhe.zhong@rivai.ai>
Date:   Tue Jan 10 06:47:26 2023 +0800

    RISC-V: Refine codes in backward fusion [NFC]
    
    This NFC patch is preparing for the following patches.
    gcc/ChangeLog:
    
            * config/riscv/riscv-vsetvl.cc (pass_vsetvl::backward_demand_fusion): Refine codes.

Diff:
---
 gcc/config/riscv/riscv-vsetvl.cc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/gcc/config/riscv/riscv-vsetvl.cc b/gcc/config/riscv/riscv-vsetvl.cc
index 9140b1832bf..f9dd7ca81ba 100644
--- a/gcc/config/riscv/riscv-vsetvl.cc
+++ b/gcc/config/riscv/riscv-vsetvl.cc
@@ -2011,15 +2011,15 @@ 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;
 
       edge e;

                 reply	other threads:[~2023-01-26 19:12 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230126191241.858FD3858C62@sourceware.org \
    --to=kito@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).