From 485d61a797e71da1fca3c9ab710643fac492197f Mon Sep 17 00:00:00 2001 From: Paul Brook Date: Tue, 6 Apr 2004 14:42:35 +0000 Subject: [PATCH] * doc/sourcebuild.texi: Remove obsolete contraint on testcases. From-SVN: r80454 --- gcc/ChangeLog | 6 +++++- gcc/doc/sourcebuild.texi | 4 ---- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index 7cf0c67666b..5bf83b553fb 100644 --- a/gcc/ChangeLog +++ b/gcc/ChangeLog @@ -1,3 +1,7 @@ +2004-04-06 Paul Brook + + * doc/sourcebuild.texi: Remove obsolete contraint on testcases. + 2004-04-05 Kaz Kojima * config/sh/sh.c (prepare_move_operands): Use emit_call_insn @@ -12,7 +16,7 @@ 2004-04-05 Caroline Tice - * gcc.c (combine_flag): New global variable, for new driver option. + * gcc.c (combine_flag): New global variable, for new driver option. (struct compiler): Add two new fields, to be used when combining multiple input files in a single pass (IMA). (default_compilers): Add values for the new fields to all diff --git a/gcc/doc/sourcebuild.texi b/gcc/doc/sourcebuild.texi index 12f40502d77..8868d193b88 100644 --- a/gcc/doc/sourcebuild.texi +++ b/gcc/doc/sourcebuild.texi @@ -820,10 +820,6 @@ been fixed, or whether it may be a regression, but does not give any other information about the bug or where discussion of it may be found. Some other language testsuites follow similar conventions. -Test cases should use @code{abort ()} to indicate failure and -@code{exit (0)} for success; on some targets these may be redefined to -indicate failure and success in other ways. - In the @file{gcc.dg} test suite, it is often necessary to test that an error is indeed a hard error and not just a warning---for example, where it is a constraint violation in the C standard, which must -- 2.30.2