public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107867] New: [13 Regression] ICE in init_from_control_deps, at gimple-predicate-analysis.cc:1699 since r13-2314-ga8ebd27d0ab69b08
Date: Fri, 25 Nov 2022 09:40:06 +0000	[thread overview]
Message-ID: <bug-107867-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107867
           Summary: [13 Regression] ICE in init_from_control_deps, at
                    gimple-predicate-analysis.cc:1699 since
                    r13-2314-ga8ebd27d0ab69b08
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: marxin at gcc dot gnu.org
                CC: rguenth at gcc dot gnu.org
  Target Milestone: ---

One more ICE with the same test-case as PR107803:

$ g++ /home/marxin/Programming/gcc/gcc/testsuite/g++.dg/pr107803.C -Wextra
-fno-tree-ccp -Os
during GIMPLE pass: uninit
/home/marxin/Programming/gcc/gcc/testsuite/g++.dg/pr107803.C: In function ‘int
main()’:
/home/marxin/Programming/gcc/gcc/testsuite/g++.dg/pr107803.C:10:1: internal
compiler error: in init_from_control_deps, at gimple-predicate-analysis.cc:1747
   10 | main()
      | ^~~~
0x947200 predicate::init_from_control_deps(vec<edge_def*, va_heap, vl_ptr>
const*, unsigned int, bool)
        /home/marxin/Programming/gcc/gcc/gimple-predicate-analysis.cc:1747
0x1f79316 predicate::init_from_control_deps(vec<edge_def*, va_heap, vl_ptr>
const*, unsigned int, bool)
        /home/marxin/Programming/gcc/gcc/gimple-predicate-analysis.cc:1722
0x1f79316 uninit_analysis::init_use_preds(predicate&, basic_block_def*,
basic_block_def*)
        /home/marxin/Programming/gcc/gcc/gimple-predicate-analysis.cc:2003
0x1f7c98f uninit_analysis::is_use_guarded(gimple*, basic_block_def*, gphi*,
unsigned int, hash_set<gphi*, false, default_hash_traits<gphi*> >*)
        /home/marxin/Programming/gcc/gcc/gimple-predicate-analysis.cc:2154
0x1f7cf7a uninit_analysis::is_use_guarded(gimple*, basic_block_def*, gphi*,
unsigned int)
        /home/marxin/Programming/gcc/gcc/gimple-predicate-analysis.cc:2195
0x1410e5c find_uninit_use
        /home/marxin/Programming/gcc/gcc/tree-ssa-uninit.cc:1234
0x141178e warn_uninitialized_phi
        /home/marxin/Programming/gcc/gcc/tree-ssa-uninit.cc:1304
0x141178e execute_late_warn_uninitialized
        /home/marxin/Programming/gcc/gcc/tree-ssa-uninit.cc:1425
0x141178e execute
        /home/marxin/Programming/gcc/gcc/tree-ssa-uninit.cc:1442
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.

             reply	other threads:[~2022-11-25  9:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25  9:40 marxin at gcc dot gnu.org [this message]
2022-11-25  9:40 ` [Bug tree-optimization/107867] " marxin at gcc dot gnu.org
2022-11-25 12:38 ` rguenth at gcc dot gnu.org
2022-11-28  8:00 ` cvs-commit at gcc dot gnu.org
2022-11-28  8:01 ` 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-107867-4@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).