public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Filip Kastl <pheeck@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/pheeck/heads/sccp)] unstuck: used as_a <gphi *>
Date: Mon, 11 Jul 2022 09:17:23 +0000 (GMT)	[thread overview]
Message-ID: <20220711091723.B7A38385829C@sourceware.org> (raw)

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

commit d27a4a2e310515fdfea6a51d80537a1a77f8b497
Author: Filip Kastl <filip.kastl@gmail.com>
Date:   Mon Jul 11 11:17:13 2022 +0200

    unstuck: used as_a <gphi *>

Diff:
---
 gcc/sccp.cc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/sccp.cc b/gcc/sccp.cc
index 752ecdbc649..23a7a38d941 100644
--- a/gcc/sccp.cc
+++ b/gcc/sccp.cc
@@ -134,8 +134,8 @@ tarjan_strongconnect (gphi *phi)
       unsigned op_vnum = SSA_NAME_VERSION (op);
       if (!vertices[op_vnum].visited)
 	{
-	  // TODO Will the next line work? Implicit gimple* -> gphi*
-	  tarjan_strongconnect (stmt);
+	  // TODO Will the next line work?
+	  tarjan_strongconnect (as_a <gphi *> (stmt));
 	  tarjan_update_lowlink (vnum, vertices[op_vnum].lowlink);
 	}
       else if (vertices[op_vnum].is_on_stack)


             reply	other threads:[~2022-07-11  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  9:17 Filip Kastl [this message]
2023-02-15 10:13 Filip Kastl

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=20220711091723.B7A38385829C@sourceware.org \
    --to=pheeck@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).