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/112303] New: ICE on valid code at -O3 on x86_64-linux-gnu: verify_flow_info failed Date: Mon, 30 Oct 2023 21:52:47 +0000 [thread overview] Message-ID: <bug-112303-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112303 Bug ID: 112303 Summary: ICE on valid code at -O3 on x86_64-linux-gnu: verify_flow_info failed 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: --- This appears to be a recent regression. Compiler Explorer: https://godbolt.org/z/9h7K8eqs8 [578] % 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.0/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.0 20231030 (experimental) (GCC) [579] % [579] % gcctk -O2 -c small.c [580] % [580] % gcctk -O3 -c small.c small.c: In function ‘j’: small.c:3:6: error: count of bb 228 not initialized 3 | int *j() { | ^ during GIMPLE pass: cunroll small.c:3:6: internal compiler error: verify_flow_info failed 0xbafcaf verify_flow_info() ../../gcc-trunk/gcc/cfghooks.cc:287 0x11718ff checking_verify_flow_info() ../../gcc-trunk/gcc/cfghooks.h:214 0x11718ff cleanup_tree_cfg_noloop ../../gcc-trunk/gcc/tree-cfgcleanup.cc:1154 0x11718ff cleanup_tree_cfg(unsigned int) ../../gcc-trunk/gcc/tree-cfgcleanup.cc:1205 0x1295dbd tree_unroll_loops_completely ../../gcc-trunk/gcc/tree-ssa-loop-ivcanon.cc:1565 0x1295ed3 execute ../../gcc-trunk/gcc/tree-ssa-loop-ivcanon.cc:1673 0x1295ed3 execute ../../gcc-trunk/gcc/tree-ssa-loop-ivcanon.cc:1663 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. [581] % [581] % cat small.c int a, b, d, e, f, **g, h; char c; int *j() { for (int i = 0; i < 3; i++) { for (h = 0; h < 2; h++) ; if (!b) break; } while (f) while (e) { c = 0; while (d) while (a) *g = j(); } return 0; }
next reply other threads:[~2023-10-30 21:52 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-30 21:52 zhendong.su at inf dot ethz.ch [this message] 2023-10-30 21:55 ` [Bug tree-optimization/112303] " zhendong.su at inf dot ethz.ch 2023-10-30 21:59 ` [Bug tree-optimization/112303] [14 Regression] " pinskia at gcc dot gnu.org 2023-10-30 22:00 ` pinskia at gcc dot gnu.org 2023-10-31 3:21 ` sjames at gcc dot gnu.org 2023-10-31 5:15 ` [Bug tree-optimization/112303] [14 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: verify_flow_info failed since r14-3459-g0c78240fd7d519 sjames at gcc dot gnu.org 2023-10-31 8:45 ` rguenth at gcc dot gnu.org 2023-10-31 11:08 ` zhendong.su at inf dot ethz.ch 2023-12-05 22:55 ` pinskia at gcc dot gnu.org 2023-12-05 23:02 ` jakub at gcc dot gnu.org 2023-12-06 7:35 ` rguenther at suse dot de 2024-03-05 11:19 ` jakub at gcc dot gnu.org 2024-03-26 10:36 ` rguenth at gcc dot gnu.org 2024-03-26 10:40 ` jakub at gcc dot gnu.org 2024-03-26 11:45 ` jakub at gcc dot gnu.org 2024-03-27 14:35 ` jakub at gcc dot gnu.org 2024-03-27 17:46 ` hubicka at ucw dot cz 2024-03-28 14:05 ` cvs-commit at gcc dot gnu.org 2024-03-30 3:55 ` cvs-commit at gcc dot gnu.org 2024-04-03 11:59 ` jakub 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-112303-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).