public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [committed] [PR rtl-optimization/107182] Clear EDGE_CROSSING for jump->ret optimization
Date: Mon, 10 Oct 2022 22:46:35 -0600	[thread overview]
Message-ID: <db08f7bd-9bb5-5ab4-ca1c-0cb5dbe851f5@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 445 bytes --]


When turning a jump to a return into a return, we need to clear 
EDGE_CROSSING of the fallthru edge to prevent a checking failure.

I considered not applying the transformation when the edge has 
EDGE_CROSSING set, but it still seems like we ought to eliminate the 
unnecessary jump in that case.


Bootstrapped and regression tested on x86_64.  Also did a profiled 
bootstrap and regression test on x86_64.


Installing on the trunk.


Jeff


[-- Attachment #2: P --]
[-- Type: text/plain, Size: 1161 bytes --]

commit db24bdc743cf23ea12d2dcf8254d86ab366bb46d
Author: Jeff Law <jeffreyalaw@gmail.com>
Date:   Tue Oct 11 00:44:26 2022 -0400

    [PR rtl-optimization/107182] Clear EDGE_CROSSING for jump->ret optimization
    
    When turning a jump to a return into a return, we need to clear EDGE_CROSSING
    of the fallthru edge to prevent a checking failure.
    
    I considered not applying the transformation when the edge has EDGE_CROSSING
    set, but it still seems like we ought to eliminate the unnecessary jump in
    that case.
    
    gcc/
            PR rtl-optimization/107182
            * cfgrtl.cc (fixup_reorder_chain): When optimizing a jump to a
            return, clear EDGE_CROSSING on the appropriate edge.

diff --git a/gcc/cfgrtl.cc b/gcc/cfgrtl.cc
index 281a432f6a6..f31941a61f9 100644
--- a/gcc/cfgrtl.cc
+++ b/gcc/cfgrtl.cc
@@ -4055,6 +4055,7 @@ fixup_reorder_chain (void)
 	  ret_label = PATTERN (ret);
 	  dest = EXIT_BLOCK_PTR_FOR_FN (cfun);
 
+	  e_fall->flags &= ~EDGE_CROSSING;
 	  /* E_FALL->dest might become unreachable as a result of
 	     replacing the jump with a return.  So arrange to remove
 	     unreachable blocks.  */

                 reply	other threads:[~2022-10-11  4:46 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=db08f7bd-9bb5-5ab4-ca1c-0cb5dbe851f5@gmail.com \
    --to=jeffreyalaw@gmail.com \
    --cc=gcc-patches@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).