This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[tree-ssa] xfail tree-ssa/20030731-1.c


Starting to clean up the two dozen tree-ssa failures, many of
which are not actually expected to pass.

The comment should be relatively explanitory -- the optimization
that we actually implement isn't strong enough to find this.


r~


        * gcc.dg/tree-ssa/20030731-1.c: XFAIL.

Index: testsuite/gcc.dg/tree-ssa/20030731-1.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/testsuite/gcc.dg/tree-ssa/Attic/20030731-1.c,v
retrieving revision 1.1.2.3
diff -c -p -d -r1.1.2.3 20030731-1.c
*** testsuite/gcc.dg/tree-ssa/20030731-1.c	7 Jan 2004 23:44:17 -0000	1.1.2.3
--- testsuite/gcc.dg/tree-ssa/20030731-1.c	4 Feb 2004 06:52:20 -0000
*************** store_expr (exp, target, want_value)
*** 58,62 ****
  /* All paths to the test "target != 0" occuring in the final IF statement
     dereference target.  Thus target can not have the value zero at that
     point and the test should have been eliminated.  */
! /* { dg-final { scan-tree-dump-times "target.*!= 0" 0 "dom3"} } */
! 
--- 58,65 ----
  /* All paths to the test "target != 0" occuring in the final IF statement
     dereference target.  Thus target can not have the value zero at that
     point and the test should have been eliminated.  */
! /* ??? The dominator walker (A) doesn't merge this data at joins and
!    (B) only looks at immediate dominators, and only queued_subexp_p
!    immediately dominates the comparison in question.  We need something
!    stronger.  */
! /* { dg-final { scan-tree-dump-times "target.*!= 0" 0 "dom3" { xfail *-*-* } } } */


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]