From: Paul Brook <paul@codesourcery.com>
Date: Tue, 6 Apr 2004 15:28:20 +0000 (+0000)
Subject: * README.gcc: Remove obsolete contraint on testcases.
X-Git-Tag: releases/gcc-4.0.0~9034
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=5f3b79c570eea5d64fbbfa90606c07ac63157321;p=thirdparty%2Fgcc.git

* README.gcc: Remove obsolete contraint on testcases.

From-SVN: r80455
---

diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index 0fcc366c937c..c7c589da9deb 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,7 @@
+2004-04-06  Paul Brook  <paul@codesourcery.com>
+
+	* README.gcc: Remove obsolete contraint on testcases.
+
 2004-04-05  Paul Brook  <paul@codesourcery.com>
 
 	PR2123
diff --git a/gcc/testsuite/README.gcc b/gcc/testsuite/README.gcc
index 17904bceae5a..f193bde54bbb 100644
--- a/gcc/testsuite/README.gcc
+++ b/gcc/testsuite/README.gcc
@@ -77,10 +77,6 @@ For IEEE FP specific tests, put them in execute/ieee.
 
 For execution tests, put them in execute.
 
-Always use abort() for runtime failures, and exit(0) for success.
-The testing harness is set up to watch for these and do something appropriate
-(when necessary) for target boards.
-
 If a test does not fit into the torture framework, use the dg framework.