From ff381240b50d651ae2a1c51e362d3cdbe9755f52 Mon Sep 17 00:00:00 2001 From: rth Date: Thu, 31 May 2001 22:06:30 +0000 Subject: [PATCH] * gcc.c-torture/execute/memcheck/blkarg.x: Disable the test. git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@42762 138bc75d-0d04-0410-961f-82ee72b054a4 --- gcc/testsuite/ChangeLog | 1 + gcc/testsuite/gcc.c-torture/execute/memcheck/blkarg.x | 9 +++++---- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog index 2b9b5ab..0c562fd 100644 --- a/gcc/testsuite/ChangeLog +++ b/gcc/testsuite/ChangeLog @@ -1,5 +1,6 @@ 2001-05-31 Richard Henderson + * 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 diff --git a/gcc/testsuite/gcc.c-torture/execute/memcheck/blkarg.x b/gcc/testsuite/gcc.c-torture/execute/memcheck/blkarg.x index 52b53fe..a56e2ca 100644 --- 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 -- 2.7.4