public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/106909] New: error: control flow in the middle of basic block Date: Mon, 12 Sep 2022 15:30:10 +0000 [thread overview] Message-ID: <bug-106909-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106909 Bug ID: 106909 Summary: error: control flow in the middle of basic block Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: dcb314 at hotmail dot com Target Milestone: --- Created attachment 53563 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53563&action=edit C++ source code The attached legal C++ code does this: $ ../results/bin/g++ -c -g -O2 -w bug847.cc /home/dcb36/rpmbuild/BUILD/capnproto-c++-0.9.1/src/capnp/../kj/parse/common.h:727:7: error: control flow in the middle of basic block 23 727 | operator()(Input& input) const { | ^~~~~~~~ /home/dcb36/rpmbuild/BUILD/capnproto-c++-0.9.1/src/capnp/../kj/parse/common.h:727:7: internal compiler error: verify_flow_info failed 0xb264bb verify_flow_info() ../../trunk.git/gcc/cfghooks.cc:284 0x109fc1b checking_verify_flow_info() ../../trunk.git/gcc/cfghooks.h:214 I will have a go at identifying a git range.
next reply other threads:[~2022-09-12 15:30 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-12 15:30 dcb314 at hotmail dot com [this message] 2022-09-12 15:43 ` [Bug tree-optimization/106909] " dcb314 at hotmail dot com 2022-09-12 15:46 ` [Bug tree-optimization/106909] [13 Regression] " pinskia at gcc dot gnu.org 2022-09-12 18:48 ` dcb314 at hotmail dot com 2022-09-12 19:49 ` [Bug tree-optimization/106909] [13 Regression] error: control flow in the middle of basic block since r13-2541-g78ef801b7263606d marxin at gcc dot gnu.org 2022-09-13 5:45 ` marxin at gcc dot gnu.org 2022-09-13 6:59 ` rguenth at gcc dot gnu.org 2022-09-13 8:52 ` cvs-commit at gcc dot gnu.org 2022-09-13 8:53 ` 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-106909-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).