public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-1939] Adjust testsuite/gcc.dg/tree-ssa/vrp-float-1.c
Date: Tue,  2 Aug 2022 19:00:26 +0000 (GMT)	[thread overview]
Message-ID: <20220802190026.574293858029@sourceware.org> (raw)

https://gcc.gnu.org/g:502605a277d36cee1b0570982a16d97a43eace67

commit r13-1939-g502605a277d36cee1b0570982a16d97a43eace67
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Tue Aug 2 20:56:49 2022 +0200

    Adjust testsuite/gcc.dg/tree-ssa/vrp-float-1.c
    
    I missed the -details dump flag, plus I wasn't checking the actual folding.
    As a bonus I had flipped the dump file name and the count, so the test
    was coming out as unresolved, which I missed because I was only checking
    for failures and passes.
    
    Whooops.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.dg/tree-ssa/vrp-float-1.c: Adjust test so it passes.

Diff:
---
 gcc/testsuite/gcc.dg/tree-ssa/vrp-float-1.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/tree-ssa/vrp-float-1.c b/gcc/testsuite/gcc.dg/tree-ssa/vrp-float-1.c
index 88faf72ac42..5be54267cf7 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/vrp-float-1.c
+++ b/gcc/testsuite/gcc.dg/tree-ssa/vrp-float-1.c
@@ -1,5 +1,5 @@
 // { dg-do compile }
-// { dg-options "-O2 -fdisable-tree-ethread -fdisable-tree-fre1 -fdump-tree-evrp" }
+// { dg-options "-O2 -fdisable-tree-ethread -fdisable-tree-fre1 -fdump-tree-evrp-details" }
 
 void bar ();
 void george ();
@@ -16,4 +16,4 @@ foo (float x, float y)
     }
 }
 
-// { dg-final { scan-tree-dump-times "Folding predicate x_*to 1" "evrp" 1 } }
+// { dg-final { scan-tree-dump-times "Folded into: if \\(1 != 0\\)" 1 "evrp" } }


                 reply	other threads:[~2022-08-02 19:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220802190026.574293858029@sourceware.org \
    --to=aldyh@gcc.gnu.org \
    --cc=gcc-cvs@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: 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).