From: Jeff Law <law@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Improve DOM's optimization of control statements
Date: Wed, 07 Oct 2015 22:06:00 -0000 [thread overview]
Message-ID: <56159768.4080400@redhat.com> (raw)
In-Reply-To: <87twq2z682.fsf@igel.home>
On 10/07/2015 04:03 PM, Andreas Schwab wrote:
> On powerpc:
>
> FAIL: gcc.c-torture/compile/pr52073.c -O2 (internal compiler error)
>
> /daten/gcc/gcc-20151006/gcc/testsuite/gcc.c-torture/compile/pr52073.c:6:1: internal compiler error: in duplicate_thread_path, at tree-ssa-threadupdate.c:2446.
> 0x10874ab7 duplicate_thread_path.
> ../../gcc/tree-ssa-threadupdate.c:2445.
> 0x10874ab7 thread_through_all_blocks(bool).
> ../../gcc/tree-ssa-threadupdate.c:2632.
> 0x107b0ea7 execute.
> ../../gcc/tree-ssa-dom.c:622.
Update your tree. This should have been fixed by:
2015-10-06 Jeff Law <law@redhat.com>
PR tree-optimization/67816
Jeff
prev parent reply other threads:[~2015-10-07 22:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 22:11 Jeff Law
2015-10-02 11:15 ` Renlin Li
2015-10-02 15:15 ` Jeff Law
2015-10-02 16:25 ` Jeff Law
2015-10-02 19:30 ` Jeff Law
2015-10-05 9:02 ` Richard Biener
2015-10-06 17:41 ` Jeff Law
2015-10-07 21:56 ` Jeff Law
2015-10-07 22:03 ` Andreas Schwab
2015-10-07 22:06 ` Jeff Law [this message]
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=56159768.4080400@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@linux-m68k.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: link
Be 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).