From: Andreas Schwab <schwab@linux-m68k.org>
To: Jeff Law <law@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][PR tree-optimization/67892] Use FSM threader to handle backedges
Date: Fri, 30 Oct 2015 14:08:00 -0000 [thread overview]
Message-ID: <87ziz08nnb.fsf@igel.home> (raw)
In-Reply-To: <5632474C.50002@redhat.com> (Jeff Law's message of "Thu, 29 Oct 2015 10:20:28 -0600")
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.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2015-10-30 13:57 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 [this message]
2015-10-30 14:34 ` Jeff Law
2015-10-30 17:56 ` Jeff Law
2015-10-30 20:20 ` Jeff Law
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=87ziz08nnb.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
/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).