public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/67816] [6 Regression] ICE in duplicate_thread_path, 186.crafty fails to build Date: Mon, 05 Oct 2015 08:26:00 -0000 [thread overview] Message-ID: <bug-67816-4-3XeVEZpfoy@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67816-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67816 --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- #1 0x0000000000ae7683 in duplicate_thread_path ( entry=<edge 0x7ffff6a37620 (79 -> 23)>, exit=<edge 0x7ffff6a07658 (58 -> 59)>, region=0x1b68550, n_region=10, region_copy=0x1b6abf0) at /space/rguenther/src/svn/trunk/gcc/tree-ssa-threadupdate.c:2445 2445 gcc_assert (i + 1 == n_region (gdb) p i $1 = 6 (gdb) p n_region $2 = 10 (gdb) p region_copy[i + 1] $3 = <basic_block 0x7ffff6a792d8 (114)> (gdb) p single_succ_edge (bb)->dest $4 = <basic_block 0x7ffff6a23c98 (53)>
next prev parent reply other threads:[~2015-10-05 8:26 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-02 10:37 [Bug tree-optimization/67816] New: " rguenth at gcc dot gnu.org 2015-10-02 10:37 ` [Bug tree-optimization/67816] " rguenth at gcc dot gnu.org 2015-10-02 10:53 ` rguenth at gcc dot gnu.org 2015-10-02 11:10 ` mpolacek at gcc dot gnu.org 2015-10-02 12:01 ` rguenther at suse dot de 2015-10-04 7:01 ` rguenther at suse dot de 2015-10-05 8:16 ` rguenth at gcc dot gnu.org 2015-10-05 8:23 ` rguenth at gcc dot gnu.org 2015-10-05 8:26 ` rguenth at gcc dot gnu.org [this message] 2015-10-05 8:35 ` trippels at gcc dot gnu.org 2015-10-05 9:01 ` trippels at gcc dot gnu.org 2015-10-05 15:25 ` law at redhat dot com 2015-10-07 2:26 ` law at redhat dot com 2015-10-07 2:26 ` law 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-67816-4-3XeVEZpfoy@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).