public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Biener <rguenth@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-565] Do not clear bb->aux in duplicate_loop_body_to_header_edge
Date: Tue, 17 May 2022 15:53:59 +0000 (GMT)	[thread overview]
Message-ID: <20220517155359.E8FFA3858D3C@sourceware.org> (raw)

https://gcc.gnu.org/g:941efd87e22b1b88e3488b8e681d14d0d66e45ac

commit r13-565-g941efd87e22b1b88e3488b8e681d14d0d66e45ac
Author: Richard Biener <rguenther@suse.de>
Date:   Tue May 17 17:18:06 2022 +0200

    Do not clear bb->aux in duplicate_loop_body_to_header_edge
    
    duplicate_loop_body_to_header_edge clears bb->aux which is not wanted
    by a new use in loop unswitching.  The clearing was introduced with
    r0-69110-g6580ee7781f903 and it seems accidentially so.
    
    2022-05-17  Richard Biener  <rguenther@suse.de>
    
            * cfgloopmanip.cc (duplicate_loop_body_to_header_edge): Do
            not clear bb->aux of the copied blocks.

Diff:
---
 gcc/cfgloopmanip.cc | 1 -
 1 file changed, 1 deletion(-)

diff --git a/gcc/cfgloopmanip.cc b/gcc/cfgloopmanip.cc
index b4357c03e86..7736e3ec709 100644
--- a/gcc/cfgloopmanip.cc
+++ b/gcc/cfgloopmanip.cc
@@ -1351,7 +1351,6 @@ duplicate_loop_body_to_header_edge (class loop *loop, edge e,
       unsigned j;
 
       bb = bbs[i];
-      bb->aux = 0;
 
       auto_vec<basic_block> dom_bbs = get_dominated_by (CDI_DOMINATORS, bb);
       FOR_EACH_VEC_ELT (dom_bbs, j, dominated)


                 reply	other threads:[~2022-05-17 15:53 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=20220517155359.E8FFA3858D3C@sourceware.org \
    --to=rguenth@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).