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 rtl-optimization/104989] New: ICE in rtl_verify_bb_insns, at cfgrtl.cc:2797 (error: flow control insn inside a basic block) Date: Sun, 20 Mar 2022 04:29:51 +0000 [thread overview] Message-ID: <bug-104989-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104989 Bug ID: 104989 Summary: ICE in rtl_verify_bb_insns, at cfgrtl.cc:2797 (error: flow control insn inside a basic block) Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rtl-optimization Assignee: unassigned at gcc dot gnu.org Reporter: asolokha at gmx dot com Target Milestone: --- g++ 12.0.1 20220313 snapshot (g:7e28750395889d16a9cba49cd5935ced7dc00ce8) ICEs when compiling gcc/testsuite/g++.dg/other/pr84964.C w/ -fnon-call-exceptions: % g++-12.0.1 -fchecking -fnon-call-exceptions -w gcc/testsuite/g++.dg/other/pr84964.C gcc/testsuite/g++.dg/other/pr84964.C: In function 'void c(...)': gcc/testsuite/g++.dg/other/pr84964.C:6:16: sorry, unimplemented: passing too large argument on stack 6 | void c(...) { c(a()); } | ~^~~~~ gcc/testsuite/g++.dg/other/pr84964.C:6:23: error: in basic block 2: 6 | void c(...) { c(a()); } | ^ gcc/testsuite/g++.dg/other/pr84964.C:6:23: error: flow control insn inside a basic block (call_insn 9 8 14 2 (call (mem:QI (symbol_ref:DI ("_Z1cz") [flags 0x3] <function_decl 0x7f451f1a4400 c>) [0 c S1 A8]) (const_int 2305843009213693952 [0x2000000000000000])) "gcc/testsuite/g++.dg/other/pr84964.C":6:16 -1 (expr_list:REG_ARGS_SIZE (const_int 0 [0]) (expr_list:REG_NORETURN (const_int 0 [0]) (nil))) (expr_list (use (reg:QI 0 ax)) (nil))) during RTL pass: expand gcc/testsuite/g++.dg/other/pr84964.C:6:23: internal compiler error: in rtl_verify_bb_insns, at cfgrtl.cc:2797 0x800d85 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*) /var/tmp/portage/sys-devel/gcc-12.0.1_p20220313/work/gcc-12-20220313/gcc/rtl-error.cc:108 0xcd5ff3 rtl_verify_bb_insns /var/tmp/portage/sys-devel/gcc-12.0.1_p20220313/work/gcc-12-20220313/gcc/cfgrtl.cc:2797 0xcde38a rtl_verify_flow_info_1 /var/tmp/portage/sys-devel/gcc-12.0.1_p20220313/work/gcc-12-20220313/gcc/cfgrtl.cc:2883 0xcde38a rtl_verify_flow_info /var/tmp/portage/sys-devel/gcc-12.0.1_p20220313/work/gcc-12-20220313/gcc/cfgrtl.cc:3126 0xcc456a verify_flow_info() /var/tmp/portage/sys-devel/gcc-12.0.1_p20220313/work/gcc-12-20220313/gcc/cfghooks.cc:282 0x1ee7578 checking_verify_flow_info /var/tmp/portage/sys-devel/gcc-12.0.1_p20220313/work/gcc-12-20220313/gcc/cfghooks.h:214 0x1ee7578 try_optimize_cfg /var/tmp/portage/sys-devel/gcc-12.0.1_p20220313/work/gcc-12-20220313/gcc/cfgcleanup.cc:2980 0x1ee7578 cleanup_cfg(int) /var/tmp/portage/sys-devel/gcc-12.0.1_p20220313/work/gcc-12-20220313/gcc/cfgcleanup.cc:3143 0xcc1f1f execute /var/tmp/portage/sys-devel/gcc-12.0.1_p20220313/work/gcc-12-20220313/gcc/cfgexpand.cc:6971
next reply other threads:[~2022-03-20 4:29 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-20 4:29 asolokha at gmx dot com [this message] 2022-03-21 8:55 ` [Bug rtl-optimization/104989] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org 2022-03-21 9:33 ` marxin at gcc dot gnu.org 2022-03-21 10:34 ` jakub at gcc dot gnu.org 2022-03-22 7:40 ` cvs-commit at gcc dot gnu.org 2022-03-22 7:43 ` [Bug rtl-optimization/104989] [9/10/11 " jakub at gcc dot gnu.org 2022-05-27 9:47 ` [Bug rtl-optimization/104989] [10/11 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2023-04-15 17:03 ` cvs-commit at gcc dot gnu.org 2023-04-16 3:18 ` sjames at gcc dot gnu.org 2023-07-07 10:42 ` [Bug rtl-optimization/104989] [11 " 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-104989-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).