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/106249] New: ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 Date: Mon, 11 Jul 2022 05:05:34 +0000 [thread overview] Message-ID: <bug-106249-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106249 Bug ID: 106249 Summary: 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: --- gfortran 13.0.0 20220710 snapshot (g:0587cef3d7962a8b0f44779589ba2920dd3d71e5) ICEs when compiling the following testcase w/ -O1 -fpeel-loops -funreachable-traps: SUBROUTINE YYPARS(LSTACK,YYPS,YYSTAT) INTEGER LSTACK,YYPS,YYSTAT INTEGER YYXI INTEGER YYEXCA(0:11) YYXI = 1 10 CONTINUE IF (YYPS .GT. LSTACK) CALL ERRORM() 30 CONTINUE IF ((YYEXCA(YYXI) .NE. (-1)) .OR. (YYEXCA(YYXI) .NE. YYSTAT)) THEN YYXI = YYXI + 2 GO TO 30 END IF GO TO 10 RETURN END % gfortran-13.0.0 -O1 -fpeel-loops -funreachable-traps -c apyn3fnn.f during GIMPLE pass: cunroll apyn3fnn.f:1:23: 1 | SUBROUTINE YYPARS(LSTACK,YYPS,YYSTAT) | ^ internal compiler error: in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 0x771827 check_loop_closed_ssa_def /var/tmp/portage/sys-devel/gcc-13.0.0_p20220710/work/gcc-13-20220710/gcc/tree-ssa-loop-manip.cc:645 0x10e97c4 check_loop_closed_ssa_bb /var/tmp/portage/sys-devel/gcc-13.0.0_p20220710/work/gcc-13-20220710/gcc/tree-ssa-loop-manip.cc:659 0x10eab26 verify_loop_closed_ssa(bool, loop*) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220710/work/gcc-13-20220710/gcc/tree-ssa-loop-manip.cc:695 0x10eab26 verify_loop_closed_ssa(bool, loop*) /var/tmp/portage/sys-devel/gcc-13.0.0_p20220710/work/gcc-13-20220710/gcc/tree-ssa-loop-manip.cc:679 0x10d24d6 tree_unroll_loops_completely /var/tmp/portage/sys-devel/gcc-13.0.0_p20220710/work/gcc-13-20220710/gcc/tree-ssa-loop-ivcanon.cc:1499 0x10d2551 execute /var/tmp/portage/sys-devel/gcc-13.0.0_p20220710/work/gcc-13-20220710/gcc/tree-ssa-loop-ivcanon.cc:1603 0x10d2551 execute /var/tmp/portage/sys-devel/gcc-13.0.0_p20220710/work/gcc-13-20220710/gcc/tree-ssa-loop-ivcanon.cc:1593
next reply other threads:[~2022-07-11 5:05 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-11 5:05 asolokha at gmx dot com [this message] 2022-07-11 5:32 ` [Bug tree-optimization/106249] [13 Regression] " pinskia at gcc dot gnu.org 2022-07-11 7:38 ` rguenth at gcc dot gnu.org 2022-07-11 7:39 ` rguenth at gcc dot gnu.org 2022-07-11 7:41 ` rguenth at gcc dot gnu.org 2022-07-12 16:10 ` asolokha at gmx dot com 2022-07-13 7:15 ` [Bug tree-optimization/106249] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 since r13-1450-gd2a898666609452e marxin at gcc dot gnu.org 2022-07-13 7:36 ` cvs-commit at gcc dot gnu.org 2022-07-13 7:36 ` rguenth at gcc dot gnu.org 2022-07-14 17:26 ` pinskia at gcc dot gnu.org 2022-07-26 9:27 ` jakub at gcc dot gnu.org 2022-12-20 14:35 ` rguenth at gcc dot gnu.org 2023-02-08 11:45 ` asolokha at gmx dot com 2023-02-10 10:17 ` 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-106249-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: linkBe 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).