public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Law <law@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-4253] Fix thinko in last patch
Date: Tue, 22 Nov 2022 23:36:04 +0000 (GMT)	[thread overview]
Message-ID: <20221122233604.333603854553@sourceware.org> (raw)

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

commit r13-4253-gee86077c2c2e38376cb5a575af62e9187c98e8df
Author: Jeff Law <jlaw@ventanamicro.com>
Date:   Tue Nov 22 16:30:38 2022 -0700

    Fix thinko in last patch
    
    gcc/
            * tree-ssa-dom.cc (record_edge_info): Fix thinko in last commit.

Diff:
---
 gcc/tree-ssa-dom.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/tree-ssa-dom.cc b/gcc/tree-ssa-dom.cc
index e82f4f73a66..c9e52d1ee94 100644
--- a/gcc/tree-ssa-dom.cc
+++ b/gcc/tree-ssa-dom.cc
@@ -676,7 +676,7 @@ record_edge_info (basic_block bb)
 		     if it never traverses the backedge to begin with.  This
 		     implies that any PHI nodes create equivalances that we
 		     can attach to the loop exit edge.  */
-		  int bool
+		  bool alternative
 		    = (EDGE_PRED (bb, 0)->flags & EDGE_DFS_BACK) ? 1 : 0;
 
 		  gphi_iterator gsi;

                 reply	other threads:[~2022-11-22 23:36 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=20221122233604.333603854553@sourceware.org \
    --to=law@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).