public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/106498] New: [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645
Date: Mon, 01 Aug 2022 10:32:08 +0000	[thread overview]
Message-ID: <bug-106498-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106498
           Summary: [13 Regression] ICE in check_loop_closed_ssa_def, at
                    tree-ssa-loop-manip.cc:645
           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: asolokha at gmx dot com
  Target Milestone: ---
            Target: powerpc-e300c3-linux-gnu

gcc 13.0.0 20220731 snapshot (g:525a1a73a5a563c829a5f76858fe122c9b39f254) ICEs
when compiling gcc/testsuite/gcc.c-torture/execute/pr71335.c for a 32-bit BE
powerpc target w/ -O1 -floop-parallelize-all -ftree-parallelize-loops=2:

% powerpc-e300c3-linux-gnu-gcc-13.0.0 -O1 -floop-parallelize-all
-ftree-parallelize-loops=2 -w -c gcc/testsuite/gcc.c-torture/execute/pr71335.c
during GIMPLE pass: ompexpssa
gcc/testsuite/gcc.c-torture/execute/pr71335.c: In function 'main':
gcc/testsuite/gcc.c-torture/execute/pr71335.c:3:1: internal compiler error: in
check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645
    3 | main ()
      | ^~~~
0x6e62f7 check_loop_closed_ssa_def
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20220731/work/gcc-13-20220731/gcc/tree-ssa-loop-manip.cc:645
0xfd3834 check_loop_closed_ssa_bb
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20220731/work/gcc-13-20220731/gcc/tree-ssa-loop-manip.cc:659
0xfd4e26 verify_loop_closed_ssa(bool, loop*)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20220731/work/gcc-13-20220731/gcc/tree-ssa-loop-manip.cc:695
0xfd4e26 verify_loop_closed_ssa(bool, loop*)
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20220731/work/gcc-13-20220731/gcc/tree-ssa-loop-manip.cc:679
0xd691a4 execute_function_todo
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20220731/work/gcc-13-20220731/gcc/passes.cc:2109
0xd695eb execute_todo
       
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-13.0.0_p20220731/work/gcc-13-20220731/gcc/passes.cc:2145

This PR can in fact be a duplicate of PR106099, or PR106249, or both.

             reply	other threads:[~2022-08-01 10:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-01 10:32 asolokha at gmx dot com [this message]
2022-08-01 11:17 ` [Bug tree-optimization/106498] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 since r13-1450-gd2a89866660945 marxin at gcc dot gnu.org
2022-08-01 13:22 ` rguenth at gcc dot gnu.org
2022-08-01 13:57 ` rguenth at gcc dot gnu.org
2022-08-02  6:40 ` cvs-commit at gcc dot gnu.org
2022-08-02  6:41 ` 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-106498-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).