1 This is a collection of tests for the C and C++ frontends of GCC. For
2 further information please check README.gcc and README.g++, though the
3 latter may not be up-to-date any more.
5 The driver that runs this testsuite is called DejaGnu and you will
6 need a current DejaGnu snapshot, which is available from
7 ftp://gcc.gnu.org/pub/gcc/infrastructure, for example.
9 Most of these tests were originally developed and/or collected by
10 Cygnus Solutions, but these days many are being added by the GCC
13 These tests are included "as is". If any of them fails, do not report
14 a bug. Bug reports for DejaGnu can go to bug-dejagnu@prep.ai.mit.edu.
15 Discussion and comments about this testsuite should be sent to
16 gcc@gcc.gnu.org; additions and changes to should go to sent to
17 gcc-patches@gcc.gnu.org.
19 The entire testsuite is invoked by `make check` at the top level of
20 the GCC tree. `make check-g++` runs the C++ testsuite only.
23 STRUCTURE OF THE TESTSUITE
25 Almost all C++ tests reside in subdirectories of g++.old-deja, based on
26 the following structure:
28 g++.benjamin Tests by Benjamin Koz
30 g++.brendan Tests by Brendan Kehoe
32 g++.eh Tests for exception handling
33 g++.ext Tests for g++ extensions
34 g++.gb Tests by Gerald Baumgartner
35 g++.jason Tests by Jason Merill
36 g++.jeff Tests by Jeffrey A Law
37 g++.martin Tests by Martin v. Löwis
38 g++.mike Tests by Mike Stump
39 g++.niklas Tests by Niklas Hallqvist
40 g++.ns Tests for namespaces
42 g++.pt Tests for templates
44 g++.robertl Tests from gcc-bugs@gcc.gnu.org, gathered by Robert Lipe
46 g++.old-deja uses a fixed driver for all g++ tests based on the old
47 DejaGnu drivers. But just because its old, doesn't mean its redundant!
48 Tests that want to use the normal dg.exp driver can be put in g++.dg instead.
49 This may be required for platform-specific tests, or tests with other
53 Finally, some random last minute notes by Mike Stump <mrs@cygnus.com>, on
54 how to run tests (in the GCC 2.7 era):
56 runtest --tool g++ --srcdir ./testsuite
60 runtest Is the name used to invoke DejaGnu. If DejaGnu is not
61 install this will be the relative path name for runtest.
63 --tool This tells DejaGnu which tool you are testing. It is
64 mainly used to find the testsuite directories for a
65 particular tool when several testsuites are in the
66 same directory. (like the gcc and g++ testsuites)
68 --srcdir This points to the top level of the directory
69 containing the sources of the testsuite. This is
70 ./testsuite if you are in the directory that has the