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] [13 Regression] ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 since r13-1450-gd2a898666609452e Date: Wed, 08 Feb 2023 11:45:06 +0000 [thread overview] Message-ID: <bug-106249-4-fFfUBsFn1D@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106249-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106249 Arseny Solokha <asolokha at gmx dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #11 from Arseny Solokha <asolokha at gmx dot com> --- Actually, testcase from comment 0 still ICEs for me, as well as its slightly modified version: subroutine foo() implicit none integer :: x integer :: a(0:1) 10 x = x + 1 20 if ((a(x) .ne. (-1)) .or. (a(x + 1) .ne. (-1))) then x = x + 1 go to 20 end if call undefined() go to 10 return end subroutine foo % gfortran-13 -O1 -fpeel-loops -funreachable-traps -c comment0.f during GIMPLE pass: cunroll comment0.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 0x7804b7 check_loop_closed_ssa_def /var/tmp/portage/sys-devel/gcc-13.0.1_p20230205/work/gcc-13-20230205/gcc/tree-ssa-loop-manip.cc:645 0x10fc384 check_loop_closed_ssa_bb /var/tmp/portage/sys-devel/gcc-13.0.1_p20230205/work/gcc-13-20230205/gcc/tree-ssa-loop-manip.cc:659 0x10fd746 verify_loop_closed_ssa(bool, loop*) /var/tmp/portage/sys-devel/gcc-13.0.1_p20230205/work/gcc-13-20230205/gcc/tree-ssa-loop-manip.cc:695 0x10fd746 verify_loop_closed_ssa(bool, loop*) /var/tmp/portage/sys-devel/gcc-13.0.1_p20230205/work/gcc-13-20230205/gcc/tree-ssa-loop-manip.cc:679 0x10e5461 tree_unroll_loops_completely /var/tmp/portage/sys-devel/gcc-13.0.1_p20230205/work/gcc-13-20230205/gcc/tree-ssa-loop-ivcanon.cc:1499 0x10e54d1 execute /var/tmp/portage/sys-devel/gcc-13.0.1_p20230205/work/gcc-13-20230205/gcc/tree-ssa-loop-ivcanon.cc:1603 0x10e54d1 execute /var/tmp/portage/sys-devel/gcc-13.0.1_p20230205/work/gcc-13-20230205/gcc/tree-ssa-loop-ivcanon.cc:1593 % gfortran-13 -O1 -fpeel-loops -funreachable-traps -c comment11.f90 during GIMPLE pass: cunroll comment11.f90:1:14: 1 | subroutine foo() | ^ internal compiler error: in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 <identical backtrace follows> % gfortran-13 -v Using built-in specs. COLLECT_GCC=gfortran-13 COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/13/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /var/tmp/portage/sys-devel/gcc-13.0.1_p20230205/work/gcc-13-20230205/configure --host=x86_64-pc-linux-gnu --build=x86_64-pc-linux-gnu --prefix=/usr --bindir=/usr/x86_64-pc-linux-gnu/gcc-bin/13 --includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/13/include --datadir=/usr/share/gcc-data/x86_64-pc-linux-gnu/13 --mandir=/usr/share/gcc-data/x86_64-pc-linux-gnu/13/man --infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/13/info --with-gxx-include-dir=/usr/lib/gcc/x86_64-pc-linux-gnu/13/include/g++-v13 --with-python-dir=/share/gcc-data/x86_64-pc-linux-gnu/13/python --enable-languages=c,c++,fortran --enable-obsolete --enable-secureplt --disable-werror --with-system-zlib --disable-nls --disable-libunwind-exceptions --enable-checking=yes --with-gcc-major-version-only --enable-esp --enable-libstdcxx-time --disable-libstdcxx-pch --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --disable-multilib --with-multilib-list=m64 --disable-fixed-point --enable-targets=all --enable-libgomp --disable-libssp --disable-libada --disable-cet --disable-systemtap --enable-valgrind-annotations --disable-vtable-verify --disable-libvtv --without-zstd --enable-lto --with-isl --disable-isl-version-check --enable-default-ssp Thread model: posix Supported LTO compression algorithms: zlib gcc version 13.0.1 20230205 (experimental) (GCC)
next prev parent reply other threads:[~2023-02-08 11:45 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-11 5:05 [Bug tree-optimization/106249] New: ICE in check_loop_closed_ssa_def, at tree-ssa-loop-manip.cc:645 asolokha at gmx dot com 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 [this message] 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-fFfUBsFn1D@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).