Hi,
the initializer value in that testcase ends up in literal pool. As
described in the testcase the optimization does currently not work in
that situation.
Committed to mainline.
Bye,
-Andreas-
2015-03-05 Andreas Krebbel <kreb...@linux.vnet.ibm.com>
* gcc.dg/tree-ssa/ssa-dom-cse-2.c:
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 867bfb2..df1b763 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
@@ -20,5 +20,5 @@ foo ()
/* See PR63679 and PR64159, if the target forces the initializer to memory then
DOM is not able to perform this optimization. */
-/* { dg-final { scan-tree-dump "return 28;" "optimized" { xfail aarch64*-*-*
alpha*-*-* hppa*-*-* powerpc*-*-* sparc*-*-* } } } */
+/* { dg-final { scan-tree-dump "return 28;" "optimized" { xfail aarch64*-*-*
alpha*-*-* hppa*-*-* powerpc*-*-* sparc*-*-* s390*-*-* } } } */
/* { dg-final { cleanup-tree-dump "optimized" } } */
