public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH][2/2] Make SCCVN use conditional equivalences
Date: Thu, 13 Aug 2015 10:56:00 -0000	[thread overview]
Message-ID: <mvma8tviiwh.fsf@hawking.suse.de> (raw)
In-Reply-To: <alpine.LSU.2.11.1508131115120.19998@zhemvz.fhfr.qr> (Richard	Biener's message of "Thu, 13 Aug 2015 11:15:48 +0200 (CEST)")

Richard Biener <rguenther@suse.de> writes:

> On Thu, 13 Aug 2015, Andreas Schwab wrote:
>
>> On m68k:
>> 
>> FAIL: gcc.dg/tree-ssa/vrp33.c scan-tree-dump vrp1 "Folding predicate.*== 1 to 0"
>> 
>> $ gcc/xgcc -B gcc/ ../gcc/testsuite/gcc.dg/tree-ssa/vrp33.c -O2 -fdump-tree-vrp1 -S
>> $ grep -c Folding *.vrp1
>> 0
>
> I suppose for logical-op-non-short-circuit you need -fno-tree-fre for
> that testcase now (which shouldn't harm for other targets).

Yes, that works, and didn't change anything on ia64 or arm64.

Andreas.

	* gcc.dg/tree-ssa/vrp33.c: Add -fno-tree-fre.

diff --git a/gcc/testsuite/gcc.dg/tree-ssa/vrp33.c b/gcc/testsuite/gcc.dg/tree-ssa/vrp33.c
index 8c8879b..75fefa4 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/vrp33.c
+++ b/gcc/testsuite/gcc.dg/tree-ssa/vrp33.c
@@ -1,5 +1,5 @@
 /* { dg-do compile } */
-/* { dg-options "-O2 -fdump-tree-vrp1" } */
+/* { dg-options "-O2 -fdump-tree-vrp1 -fno-tree-fre" } */
 
 /* This is from PR14052.  */
 
-- 
2.5.0

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

  reply	other threads:[~2015-08-13 10:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  9:15 Richard Biener
2015-08-12 14:23 ` Richard Biener
2015-08-13  9:15   ` Andreas Schwab
2015-08-13  9:25     ` Richard Biener
2015-08-13 10:56       ` Andreas Schwab [this message]
2015-08-13  9:55   ` Andreas Schwab
2015-08-13 10:00     ` Richard Biener
2015-08-24 12:50     ` Rainer Orth
2015-08-24 12:54       ` Andreas Schwab
2015-08-16 19:02   ` H.J. Lu

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=mvma8tviiwh.fsf@hawking.suse.de \
    --to=schwab@suse.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).