public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/57103] New: [4.8/4.9 Regression] ICE: verify_gimple failed: location references block not in block tree with -ftree-parallelize-loops=4 Date: Sun, 28 Apr 2013 15:37:00 -0000 [thread overview] Message-ID: <bug-57103-4@http.gcc.gnu.org/bugzilla/> (raw) http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57103 Bug #: 57103 Summary: [4.8/4.9 Regression] ICE: verify_gimple failed: location references block not in block tree with -ftree-parallelize-loops=4 Classification: Unclassified Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end AssignedTo: unassigned@gcc.gnu.org ReportedBy: zsojka@seznam.cz Created attachment 29964 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29964 reduced testcase Compiler output: $ gcc -O -ftree-parallelize-loops=4 testcase.c testcase.c: In function 'bar._loopfn.0': testcase.c:7:3: error: location references block not in block tree for (; i < 1024; i++) ^ *d_4[i.5_25] # VUSE <.MEM_33(D)> _27 = *d_4[i.5_25]; testcase.c:7:3: internal compiler error: verify_gimple failed 0xa5e09c verify_gimple_in_cfg(function*) /mnt/svn/gcc-trunk/gcc/tree-cfg.c:4792 0x947c07 execute_function_todo /mnt/svn/gcc-trunk/gcc/passes.c:1969 0x948567 execute_todo /mnt/svn/gcc-trunk/gcc/passes.c:2002 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. Tested revisions: r198366 - crash 4.8 r198018 - crash 4.7 r198018 - OK
next reply other threads:[~2013-04-28 15:37 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-28 15:37 zsojka at seznam dot cz [this message] 2013-04-29 8:08 ` [Bug middle-end/57103] " rguenth at gcc dot gnu.org 2013-04-29 13:11 ` mpolacek at gcc dot gnu.org 2013-04-29 14:14 ` 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-57103-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).