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/106866] [13 Regression] ICE in predicate::init_from_control_deps
Date: Wed, 07 Sep 2022 10:00:31 +0000	[thread overview]
Message-ID: <bug-106866-4-9irZzRccrt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106866-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hubicka at gcc dot gnu.org

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
So somehow we late figure bar() doesn't return abnormally and thus DSE
eliminates a call to it but doesn't trigger

  if (need_ab_cleanup && stmt_can_make_abnormal_goto (stmt))
    bitmap_set_bit (need_ab_cleanup, bb->index);

which means when we either set ECF_LEAF to the function or cleared
cfun->calls_setjmp (the recursive invocation) we should have pruned
abnormal edges but we failed to.  That ends us with a block like

;;   basic block 4, loop depth 0
;;    pred:       12
;;                5
  # uninitialized_2(ab) = PHI <uninitialized_5(12), uninitialized_3(ab)(5)>
  goto <bb 11>; [99.96%]
;;    succ:       11
;;                5

where the 4->5 edge is abnormal but there's no stmt in this block that
could be responsible for it.  We also fail to verify ICE here.

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07  4:08 [Bug tree-optimization/106866] New: " asolokha at gmx dot com
2022-09-07  8:59 ` [Bug tree-optimization/106866] " rguenth at gcc dot gnu.org
2022-09-07  9:14 ` rguenth at gcc dot gnu.org
2022-09-07 10:00 ` rguenth at gcc dot gnu.org [this message]
2022-09-07 12:17 ` cvs-commit at gcc dot gnu.org
2022-09-07 12:18 ` 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-106866-4-9irZzRccrt@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).