PATCH: Update testsuite README

Mark Mitchell mark@codesourcery.com
Mon Feb 24 22:03:00 GMT 2003


This patch tries to remove out-of-date gunk in testsuite/README.

Applied on the mainline.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

2003-02-24  Mark Mitchell  <mark@codesourcery.com>

	* README: Remove out-of-date information.

Index: README
===================================================================
RCS file: /cvs/gcc/gcc/gcc/testsuite/README,v
retrieving revision 1.7
retrieving revision 1.8
diff -c -5 -p -r1.7 -r1.8
*** README	28 Jan 2003 17:05:33 -0000	1.7
--- README	24 Feb 2003 22:01:56 -0000	1.8
***************
*** 1,31 ****
! This is a collection of tests for the C and C++ frontends of GCC. For
! further information please check README.gcc and README.g++, though the
! latter may not be up-to-date any more.
  
  The driver that runs this testsuite is called DejaGnu and you will
  need a current DejaGnu snapshot, which is available from
  ftp://gcc.gnu.org/pub/gcc/infrastructure, for example.
  
- Most of these tests were originally developed and/or collected by
- Cygnus Solutions, but these days many are being added by the GCC
- developers.
- 
  These tests are included "as is". If any of them fails, do not report
  a bug.  Bug reports for DejaGnu can go to bug-dejagnu@prep.ai.mit.edu.
  Discussion and comments about this testsuite should be sent to
  gcc@gcc.gnu.org; additions and changes to should go to sent to
  gcc-patches@gcc.gnu.org.
  
  The entire testsuite is invoked by `make check` at the top level of
  the GCC tree. `make check-g++` runs the C++ testsuite only.
  
  
! STRUCTURE OF THE TESTSUITE
  
! Almost all C++ tests reside in subdirectories of g++.old-deja, based on
! the following structure:
  
    g++.benjamin	Tests by Benjamin Koz
    g++.bob
    g++.brendan	Tests by Brendan Kehoe
    g++.bugs
--- 1,28 ----
! This is a collection of tests for GCC. For further information about
! the C testsuite, see README.gcc.
  
  The driver that runs this testsuite is called DejaGnu and you will
  need a current DejaGnu snapshot, which is available from
  ftp://gcc.gnu.org/pub/gcc/infrastructure, for example.
  
  These tests are included "as is". If any of them fails, do not report
  a bug.  Bug reports for DejaGnu can go to bug-dejagnu@prep.ai.mit.edu.
  Discussion and comments about this testsuite should be sent to
  gcc@gcc.gnu.org; additions and changes to should go to sent to
  gcc-patches@gcc.gnu.org.
  
  The entire testsuite is invoked by `make check` at the top level of
  the GCC tree. `make check-g++` runs the C++ testsuite only.
  
+ STRUCTURE OF THE G++ TESTSUITE
+ 
+   g++.dg tests:
  
!   All new tests should be placed in an appropriate subdirectory of g++.dg.
  
!   g++.old-deja tests:
  
    g++.benjamin	Tests by Benjamin Koz
    g++.bob
    g++.brendan	Tests by Brendan Kehoe
    g++.bugs
*************** the following structure:
*** 41,57 ****
    g++.other
    g++.pt  	Tests for templates
    g++.rfg
    g++.robertl	Tests from gcc-bugs@gcc.gnu.org, gathered by Robert Lipe
  	
- g++.old-deja uses a fixed driver for all g++ tests based on the old
- DejaGnu drivers. But just because its old, doesn't mean its redundant!
- Tests that want to use the normal dg.exp driver can be put in g++.dg instead.
- This may be required for platform-specific tests, or tests with other
- special requirements.
- 
- 
  Finally, some random last minute notes by Mike Stump <mrs@cygnus.com>, on
  how to run tests (in the GCC 2.7 era):
  
  	runtest --tool g++ --srcdir ./testsuite
  
--- 38,47 ----



More information about the Gcc-patches mailing list