public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/107182] [13 Regression] Commit r13-2871-g1b74b5cb4e9d7191f298245063a8f9c3a1bbeff4 breaks profiledbootstrap
Date: Tue, 11 Oct 2022 04:45:52 +0000	[thread overview]
Message-ID: <bug-107182-4-M4kNqcQeVC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107182-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107182

--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jeff Law <law@gcc.gnu.org>:

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

commit r13-3211-gdb24bdc743cf23ea12d2dcf8254d86ab366bb46d
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.

  parent reply	other threads:[~2022-10-11  4:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 15:05 [Bug bootstrap/107182] New: " sirl at gcc dot gnu.org
2022-10-07 15:06 ` [Bug bootstrap/107182] " sirl at gcc dot gnu.org
2022-10-07 17:02 ` [Bug rtl-optimization/107182] [13 Regression] " pinskia at gcc dot gnu.org
2022-10-07 20:59 ` law at gcc dot gnu.org
2022-10-07 21:46 ` law at gcc dot gnu.org
2022-10-11  4:45 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-11  4:46 ` law at gcc dot gnu.org

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=bug-107182-4-M4kNqcQeVC@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).