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/57075] New: verify_flow_info failed: control flow in the middle of basic block Date: Thu, 25 Apr 2013 20:20:00 -0000 [thread overview] Message-ID: <bug-57075-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57075 Bug #: 57075 Summary: verify_flow_info failed: control flow in the middle of basic block Classification: Unclassified Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned@gcc.gnu.org ReportedBy: dcb314@hotmail.com Created attachment 29942 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29942 C source code I just tried to compile the package jam-2.5-14 on gcc-4.9 trunk dated 20130425 on an AMD x86_64 box. The compiler said execunix.c: In function 'execcmd': execunix.c:322:1: error: control flow in the middle of basic block 10 } ^ execunix.c:322:1: error: control flow in the middle of basic block 10 execunix.c:322:1: error: control flow in the middle of basic block 10 execunix.c:322:1: internal compiler error: verify_flow_info failed 0x5f9ae1 verify_flow_info() ../../src/trunk/gcc/cfghooks.c:260 0x91dec4 cleanup_tree_cfg_noloop ../../src/trunk/gcc/tree-cfgcleanup.c:693 0x91dec4 cleanup_tree_cfg() ../../src/trunk/gcc/tree-cfgcleanup.c:742 0x84be64 execute_function_todo ../../src/trunk/gcc/passes.c:1921 0x84c7e7 execute_todo ../../src/trunk/gcc/passes.c:1996 Please submit a full bug report, with preprocessed source if appropriate. Please include the complete backtrace with any bug report. See <http://gcc.gnu.org/bugs.html> for instructions. Preprocessed source code attached. Flag -O2 required.
next reply other threads:[~2013-04-25 20:20 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-25 20:20 dcb314 at hotmail dot com [this message] 2013-04-26 8:56 ` [Bug c/57075] [4.9 Regression] " mpolacek at gcc dot gnu.org 2013-04-26 10:24 ` mpolacek at gcc dot gnu.org 2013-04-26 11:34 ` [Bug tree-optimization/57075] " rguenth at gcc dot gnu.org 2013-04-26 12:03 ` mpolacek at gcc dot gnu.org 2013-04-26 12:11 ` rguenther at suse dot de 2013-04-29 12:58 ` rguenth at gcc dot gnu.org 2013-04-29 15:06 ` 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-57075-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).