* gcc.c-torture/execute/memcheck/blkarg.x: Disable the test.

From-SVN: r42762

diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 2b9b5ab3f135fbc87f56cecb7a4608d7a918e5e5..0c562fdffa21080062e97a78a573dccc29915362 100644 (file)
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,5 +1,6 @@
 2001-05-31  Richard Henderson  <rth@redhat.com>
 
+       * gcc.c-torture/execute/memcheck/blkarg.x: Disable the test.
        * g++.dg/mangle1.C: Tweek expected mangling for 64-bit hosts.
 
 2001-05-30  David.Billinghurst  <David.Billinghurst@riotinto.com>

diff --git a/gcc/testsuite/gcc.c-torture/execute/memcheck/blkarg.x b/gcc/testsuite/gcc.c-torture/execute/memcheck/blkarg.x
index 52b53fe2163851d519e6686258aaa7e5899f1846..a56e2ca59b76c9a713d8585df2001a1021a7f833 100644 (file)
--- a/gcc/testsuite/gcc.c-torture/execute/memcheck/blkarg.x
+++ b/gcc/testsuite/gcc.c-torture/execute/memcheck/blkarg.x
@@ -1,9 +1,10 @@
-# The memeory checking code does not mark the stack as readable or writable
+# The memory checking code does not mark the stack as readable or writable
 # so this test fails.  Ideally the memory checking library ought to 
 # cooperate with the host OS to mark the stack as it is used or individual
 # function prologues and epilogues ought to mark their pieces of stack as 
 # writable and readable-after-written.
 
-set torture_execute_xfail "*-*-*"
-
-return 0
+# Setting XFAIL here creates noise because the test passes at
+# random optimization levels for quite a number of targets.
+# Don't run the test at all.
+return 1