From: Jeff Law <law@redhat.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][PR tree-optimization/67892] Use FSM threader to handle backedges
Date: Fri, 30 Oct 2015 20:20:00 -0000 [thread overview]
Message-ID: <5633C82A.1080800@redhat.com> (raw)
In-Reply-To: <87ziz08nnb.fsf@igel.home>
On 10/30/2015 07:57 AM, Andreas Schwab wrote:
> I'm getting this regression on m68k:
>
> FAIL: gcc.dg/tree-ssa/ssa-thread-11.c scan-tree-dump vrp2 "FSM"
>
> The generated code looks equivalent, though.
How cool. This test also shows the FSM bits creating an irreducible
loop in cases where it's no likely profitable.
So two things to dig into now...
jeff
next prev parent reply other threads:[~2015-10-30 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 16:20 Jeff Law
2015-10-30 14:08 ` Andreas Schwab
2015-10-30 14:34 ` Jeff Law
2015-10-30 17:56 ` Jeff Law
2015-10-30 20:20 ` Jeff Law [this message]
2015-10-30 20:45 ` Jeff Law
2015-11-02 9:43 ` Richard Biener
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=5633C82A.1080800@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).