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 r14-186] Avoid repeated forwarder_block_p calls in CFG cleanup Date: Mon, 24 Apr 2023 07:26:24 +0000 (GMT) [thread overview] Message-ID: <20230424072624.589D53858D32@sourceware.org> (raw) https://gcc.gnu.org/g:28c06d0ed134d7d325da101e7e4230067cebeab3 commit r14-186-g28c06d0ed134d7d325da101e7e4230067cebeab3 Author: Richard Biener <rguenther@suse.de> Date: Wed Apr 19 11:24:00 2023 +0200 Avoid repeated forwarder_block_p calls in CFG cleanup CFG cleanup maintains BB_FORWARDER_BLOCK and uses FORWARDER_BLOCK_P to check that apart from two places which use forwarder_block_p in outgoing_edges_match alongside many BB_FORWARDER_BLOCK uses. The following adjusts those. * cfgcleanup.cc (outgoing_edges_match): Use FORWARDER_BLOCK_P. Diff: --- gcc/cfgcleanup.cc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/cfgcleanup.cc b/gcc/cfgcleanup.cc index 78f59e99653..5f1aa29c89d 100644 --- a/gcc/cfgcleanup.cc +++ b/gcc/cfgcleanup.cc @@ -1861,9 +1861,9 @@ outgoing_edges_match (int mode, basic_block bb1, basic_block bb2) /* fallthru edges must be forwarded to the same destination. */ if (fallthru1) { - basic_block d1 = (forwarder_block_p (fallthru1->dest) + basic_block d1 = (FORWARDER_BLOCK_P (fallthru1->dest) ? single_succ (fallthru1->dest): fallthru1->dest); - basic_block d2 = (forwarder_block_p (fallthru2->dest) + basic_block d2 = (FORWARDER_BLOCK_P (fallthru2->dest) ? single_succ (fallthru2->dest): fallthru2->dest); if (d1 != d2)
reply other threads:[~2023-04-24 7:26 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=20230424072624.589D53858D32@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: linkBe 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).