diff mbox

[PR,tree-optimization/71316] Fix expected output in testcase after recent threading changes

Message ID 1dae7fe7-8865-00f4-2f62-a650ed27be6d@redhat.com
State New
Headers show

Commit Message

Jeff Law June 3, 2016, 11:17 p.m. UTC 
As outlined in the BZ, this test was partially compromised by the recent 
threading changes.  Those changes result in a jump thread being found 
during VRP1 rather than DOM2 (ie, earlier in the pipeline, which is 
good).  The expected output needed tweaking for the 
logical-op-short-circuit targets.

Installed on the trunk after verifying ppc64le passes the test.

Jeff
commit c1489ff56ba84d35a076117ca923261e24b01ce2
Author: law <law@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Fri Jun 3 23:12:39 2016 +0000

    	PR tree-optimization/71316
    	* gcc.dg/tree-ssa/ssa-dom-thread-4.c: Update expected output.
    
    git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@237083 138bc75d-0d04-0410-961f-82ee72b054a4
diff mbox

Patch

diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 1a80a9c..cd45cda 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,8 @@ 
+2016-06-03  Jeff Law  <law@redhat.com>
+
+	PR tree-optimization/71316
+	* gcc.dg/tree-ssa/ssa-dom-thread-4.c: Update expected output.
+
 2016-06-03  Jakub Jelinek  <jakub@redhat.com>
 
 	* gcc.dg/vect/vect-live-1.c: Remove dg-options.  Add
diff --git a/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-4.c b/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-4.c
index 4258fb5..2dd9177 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-4.c
+++ b/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-4.c
@@ -1,5 +1,5 @@ 
 /* { dg-do compile } */ 
-/* { dg-options "-O2 -fdump-tree-dom2-details -std=gnu89" } */
+/* { dg-options "-O2 -fdump-tree-vrp1-details -fdump-tree-dom2-details -std=gnu89" } */
 struct bitmap_head_def;
 typedef struct bitmap_head_def *bitmap;
 typedef const struct bitmap_head_def *const_bitmap;
@@ -76,8 +76,7 @@  bitmap_ior_and_compl (bitmap dst, const_bitmap a, const_bitmap b,
 	 skipping the known-true "b_elt && kill_elt" in the second
 	 condition.
 
-   However, 3 of those 4 opportunities are ultimately eliminated by
-   DOM optimizing away conditionals.  So there's only one jump threading
-   opportunity left.  */
-/* { dg-final { scan-tree-dump-times "Threaded" 1 "dom2" { target logical_op_short_circuit } } } */
+   The !b_elt cases are picked up by VRP1 as jump threads.  The others
+   are optimized by DOM.  */
+/* { dg-final { scan-tree-dump-times "Threaded" 2 "vrp1" { target logical_op_short_circuit } } } */