public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/114792] New: ICE on valid code at -O1 with "-fno-tree-ccp -fno-tree-copy-prop" on x86_64-linux-gnu: in get_loop_body, at cfgloop.cc:903 Date: Sun, 21 Apr 2024 11:39:55 +0000 [thread overview] Message-ID: <bug-114792-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114792 Bug ID: 114792 Summary: ICE on valid code at -O1 with "-fno-tree-ccp -fno-tree-copy-prop" on x86_64-linux-gnu: in get_loop_body, at cfgloop.cc:903 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: zhendong.su at inf dot ethz.ch Target Milestone: --- It appears to be a recent regression and does not reproduce with 13.2. Compiler Explorer: https://godbolt.org/z/zzdjrb599 [522] % gcctk -v Using built-in specs. COLLECT_GCC=gcctk COLLECT_LTO_WRAPPER=/local/suz-local/software/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/14.0.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: ../gcc-trunk/configure --disable-bootstrap --enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk --enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib Thread model: posix Supported LTO compression algorithms: zlib gcc version 14.0.1 20240421 (experimental) (GCC) [523] % [523] % gcctk -O1 -fno-tree-ccp -fno-tree-copy-prop small.c during GIMPLE pass: ch small.c: In function ‘main’: small.c:2:5: internal compiler error: in get_loop_body, at cfgloop.cc:903 2 | int main() { | ^~~~ 0x7926fd get_loop_body(loop const*) ../../gcc-trunk/gcc/cfgloop.cc:903 0xbfbce9 unloop(loop*, bool*, bitmap_head*) ../../gcc-trunk/gcc/cfgloopmanip.cc:1014 0x12ee996 unloop_loops(vec<loop*, va_heap, vl_ptr>&, vec<int, va_heap, vl_ptr>&, vec<edge_def*, va_heap, vl_ptr>&, bitmap_head*, bool*) ../../gcc-trunk/gcc/tree-ssa-loop-ivcanon.cc:688 0x12dfc84 copy_headers ../../gcc-trunk/gcc/tree-ssa-loop-ch.cc:1158 0x12e02da execute ../../gcc-trunk/gcc/tree-ssa-loop-ch.cc:1179 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. [524] % [524] % cat small.c int a; int main() { int b = -1, c; for (; b >= 0; b++) { for (c = 0; c; c++) { L: while (a) if (a) goto L; } } return 0; }
next reply other threads:[~2024-04-21 11:39 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-21 11:39 zhendong.su at inf dot ethz.ch [this message] 2024-04-21 15:33 ` [Bug tree-optimization/114792] " hjl.tools at gmail dot com 2024-04-21 20:25 ` [Bug tree-optimization/114792] [14 Regression] " pinskia at gcc dot gnu.org 2024-04-21 20:26 ` pinskia at gcc dot gnu.org 2024-04-22 7:17 ` jakub at gcc dot gnu.org 2024-04-24 13:04 ` rguenth at gcc dot gnu.org 2024-04-24 13:05 ` rguenth at gcc dot gnu.org 2024-04-25 5:45 ` rguenth at gcc dot gnu.org 2024-04-25 6:13 ` rguenth at gcc dot gnu.org 2024-04-25 6:14 ` rguenth at gcc dot gnu.org 2024-04-25 13:20 ` cvs-commit at gcc dot gnu.org 2024-04-25 13:21 ` 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-114792-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).