]> git.ipfire.org Git - thirdparty/gcc.git/commitdiff
re PR testsuite/86540 (pr77445-2.c and ssa-dom-thread-7.c regressions since May 20...
authorJeff Law <law@redhat.com>
Thu, 6 Dec 2018 15:35:34 +0000 (08:35 -0700)
committerJeff Law <law@gcc.gnu.org>
Thu, 6 Dec 2018 15:35:34 +0000 (08:35 -0700)
PR testsuite/86540
* gcc.dg/tree-ssa/ssa-dom-thread-7.c: Skip the post switch conversion
tests on aarch64.
* gcc.dg/tree-ssa/pr77445-2.c: Similarly.

From-SVN: r266857

gcc/testsuite/ChangeLog
gcc/testsuite/gcc.dg/tree-ssa/pr77445-2.c
gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-7.c

index 1adb751cd34bd6fe8c0ba5778bffb599c1c82a9b..0272bbe06050ba2388c0a92043958522f2a02999 100644 (file)
@@ -1,3 +1,10 @@
+2018-12-06  Jeff Law  <law@redhat.com>
+
+       PR testsuite/86540
+       * gcc.dg/tree-ssa/ssa-dom-thread-7.c: Skip the post switch conversion
+       tests on aarch64.
+       * gcc.dg/tree-ssa/pr77445-2.c: Similarly.
 2018-12-06  David Malcolm  <dmalcolm@redhat.com>
 
        PR c++/85110
index eecfc4b195a9b9698e60a24aa66983d360da6f7a..c5d567dabdc5fad3f49cb6b944a676f1be1f14e3 100644 (file)
@@ -118,10 +118,14 @@ enum STATES FMS( u8 **in , u32 *transitions) {
 
 /* The profile is not updated perfectly because it is inconsitent from
    profile estimation stage. But the number of inconsistencies should not
-   increase much.  */
+   increase much. 
+
+   aarch64 has the highest CASE_VALUES_THRESHOLD in GCC.  It's high enough
+   to change decisions in switch expansion which in turn can expose new
+   jump threading opportunities.  Skip the later tests on aarch64.  */
 /* { dg-final { scan-tree-dump "Jumps threaded: 1\[1-9\]" "thread1" } } */
 /* { dg-final { scan-tree-dump-times "Invalid sum" 3 "thread1" } } */
 /* { dg-final { scan-tree-dump-not "not considered" "thread1" } } */
 /* { dg-final { scan-tree-dump-not "not considered" "thread2" } } */
-/* { dg-final { scan-tree-dump-not "not considered" "thread3" } } */
-/* { dg-final { scan-tree-dump-not "not considered" "thread4" } } */
+/* { dg-final { scan-tree-dump-not "not considered" "thread3" { target { ! aarch64*-*-* } } } } */
+/* { dg-final { scan-tree-dump-not "not considered" "thread4" { target { ! aarch64*-*-* } } } } */ 
index e395de26ec0d6c10cb1a5f56fc1a6125a3b3a771..f833aa4351deb440c4eb6a4bcfa3421670bd68cb 100644 (file)
@@ -3,8 +3,11 @@
 /* { dg-final { scan-tree-dump "Jumps threaded: 16"  "thread1" } } */
 /* { dg-final { scan-tree-dump "Jumps threaded: 9" "thread2" } } */
 /* { dg-final { scan-tree-dump "Jumps threaded: 1"  "dom2" } } */
-/* { dg-final { scan-tree-dump-not "Jumps threaded"  "dom3" } } */
-/* { dg-final { scan-tree-dump-not "Jumps threaded"  "vrp2" } } */
+/* aarch64 has the highest CASE_VALUES_THRESHOLD in GCC.  It's high enough
+   to change decisions in switch expansion which in turn can expose new
+   jump threading opportunities.  Skip the later tests on aarch64.  */
+/* { dg-final { scan-tree-dump-not "Jumps threaded"  "dom3" { target { ! aarch64*-*-* } } } } */
+/* { dg-final { scan-tree-dump-not "Jumps threaded"  "vrp2" { target { ! aarch64*-*-* } } } } */
 
 /* Most architectures get 3 threadable paths here, whereas aarch64 and
    possibly others get 5.  We really should rewrite threading tests to