The test case works on S/390 too, but only with -march=z13 or
later (i.e. if Gcc can make use of hardware vector support).
Otherwise the optimization gets too complex. The attached patch
forces Gcc to use -march=z13 instead of xfail'ing the test on
S/390.
What do you think about this approach?
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
IBM Germany
gcc/testsuite/ChangeLog
* gcc.dg/tree-ssa/ssa-dom-cse-2.c: Require a hardware vector support for
test to succeed.
>From d855b255132d6a3ef46571e84aa75c95d8c3c737 Mon Sep 17 00:00:00 2001
From: Dominik Vogt <v...@linux.vnet.ibm.com>
Date: Wed, 27 Jan 2016 08:55:03 +0100
Subject: [PATCH] S/390: Require a hardware vector support for test to
succeed.
---
gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-cse-2.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-cse-2.c b/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-cse-2.c
index 2349400..f68b53b 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-cse-2.c
+++ b/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-cse-2.c
@@ -1,5 +1,9 @@
/* { dg-do compile } */
/* { dg-options "-O3 -fno-tree-fre -fno-tree-pre -fdump-tree-optimized --param sra-max-scalarization-size-Ospeed=32" } */
+/* S390 needs hardware vector support for this to work (the optimization gets
+ * too complex without it.
+ * { dg-additional-options "-march=z13" { target { s390*-*-* } } } */
+
int
foo ()
--
2.3.0
