public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth 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 08:44:26 +0000	[thread overview]
Message-ID: <bug-106860-4-UP7ScuUI2j@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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|unassigned at gcc dot gnu.org      |rguenth at gcc dot gnu.org
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2022-09-07
   Target Milestone|---                         |12.3
             Status|UNCONFIRMED                 |ASSIGNED

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.

static bool
split_loop (class loop *loop1)
{
...
        /* Fix first loop's exit probability after scaling.  */
        edge exit_to_latch1 = single_pred_edge (loop1->latch);

I think it's a misconception that latches are guaranteed to have a single
predecessor.  With LOOPS_HAVE_SIMPLE_LATCHES we have a single _successor_.

The CFG is also very different than expected, with a lot of code on the
"latch" (a whole subloop is there).

  reply	other threads:[~2022-09-07  8:44 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 ` rguenth at gcc dot gnu.org [this message]
2022-09-07 10:09 ` [Bug tree-optimization/106860] " cvs-commit at gcc dot gnu.org
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-UP7ScuUI2j@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).