1 This is a collection of tests for GCC. For further information about
2 the C testsuite, see README.gcc.
4 The driver that runs this testsuite is called DejaGnu and you will
5 need a current DejaGnu snapshot, which is available from
6 ftp://gcc.gnu.org/pub/gcc/infrastructure, for example.
8 These tests are included "as is". If any of them fails, do not report
9 a bug. Bug reports for DejaGnu can go to bug-dejagnu@prep.ai.mit.edu.
10 Discussion and comments about this testsuite should be sent to
11 gcc@gcc.gnu.org; additions and changes to should go to sent to
12 gcc-patches@gcc.gnu.org.
14 The entire testsuite is invoked by `make check` at the top level of
15 the GCC tree. `make check-g++` runs the C++ testsuite only.
17 STRUCTURE OF THE G++ TESTSUITE
21 All new tests should be placed in an appropriate subdirectory of g++.dg.
25 g++.benjamin Tests by Benjamin Koz
27 g++.brendan Tests by Brendan Kehoe
29 g++.eh Tests for exception handling
30 g++.ext Tests for g++ extensions
31 g++.gb Tests by Gerald Baumgartner
32 g++.jason Tests by Jason Merill
33 g++.jeff Tests by Jeffrey A Law
34 g++.martin Tests by Martin v. Löwis
35 g++.mike Tests by Mike Stump
36 g++.niklas Tests by Niklas Hallqvist
37 g++.ns Tests for namespaces
39 g++.pt Tests for templates
41 g++.robertl Tests from gcc-bugs@gcc.gnu.org, gathered by Robert Lipe
43 Finally, some random last minute notes by Mike Stump <mrs@cygnus.com>, on
44 how to run tests (in the GCC 2.7 era):
46 runtest --tool g++ --srcdir ./testsuite
50 runtest Is the name used to invoke DejaGnu. If DejaGnu is not
51 install this will be the relative path name for runtest.
53 --tool This tells DejaGnu which tool you are testing. It is
54 mainly used to find the testsuite directories for a
55 particular tool when several testsuites are in the
56 same directory. (like the gcc and g++ testsuites)
58 --srcdir This points to the top level of the directory
59 containing the sources of the testsuite. This is
60 ./testsuite if you are in the directory that has the