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 tree-optimization/106860] [12/13 Regression] ICE in single_pred_edge, at basic-block.h:347
Date: Wed, 07 Sep 2022 10:09:15 +0000	[thread overview]
Message-ID: <bug-106860-4-qbNhAonOjz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106860-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:0386609923577e07354ee63754795b2f729e7e00

commit r13-2514-g0386609923577e07354ee63754795b2f729e7e00
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Sep 7 10:44:33 2022 +0200

    tree-optimization/106860 - fix profile scaling in split_loop

    The following fixes a mistake in loop splitting which assumes loop
    latches have a single predecessor and that edge is from the exit
    test.  Instead work from the single exit edge we have to find the
    edge towards the latch.

            PR tree-optimization/106860
            * tree-ssa-loop-split.cc (split_loop): Find the exit to
            latch edge from the loop exit edge instead of from the
            latch.  Verify we're going to find it.

            * g++.dg/opt/pr106860.C: New testcase.

  parent reply	other threads:[~2022-09-07 10:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06 17:17 [Bug c/106860] New: " gscfq@t-online.de
2022-09-07  8:44 ` [Bug tree-optimization/106860] " rguenth at gcc dot gnu.org
2022-09-07 10:09 ` cvs-commit at gcc dot gnu.org [this message]
2022-09-07 10:09 ` [Bug tree-optimization/106860] [12 " rguenth at gcc dot gnu.org
2022-09-09  9:50 ` cvs-commit at gcc dot gnu.org
2022-09-09  9:51 ` rguenth 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-106860-4-qbNhAonOjz@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).