  This is a collection of tests for G++ and GCC. The GCC tests come from
the C-torture test version 1.11. The G++ tests were developed by
Cygnus Support. These tests are included "as is". If any of the tests
fail, don't report a GCC bug. Bug reports for DejaGnu can go to
bug-dejagnu@prep.ai.mit.edu.

  In the future, all testsuites get released and maintained by the
devlopment team for that tool. These testsuites are included at this
time with the DejaGnu release to start the process of going through
all the tests and verifing their accuracy. 

  Since these are part of the development source tree at Cygnus, this
tar file is supposed to be untarred so that the the testsuite
directory is in the gcc source tree. Most of the time DejaGnu is run
by hand using "runtest", but as we believe in solid testing, we've
integrated it into our Makefile's as a target. We normally use these
testsuites by doing a "make all; make check" at the top level and
building and testing our whole tree.

  In the main gcc directory, there is a Makefile.in. This has the new 
target added called "make check". If it is merged into your existing
gcc/Makefile.in then it'll work like the other GNU tools.

  DejaGnu can be run either installed, or uninstalled. Usually it gets
installed so that anyone can just run the tests without having to
configure or build DejaGnu.

  To run the tests, type this while in the same directory as this README.
"[srcdir path]/runtest --all --tool gcc --srcdir ./testsuite"

Here's a brief explanation.
runtest 	- Is the name used to invoke DejaGnu. [srcdir path]
		  points to the directory where DejaGnu is. This is
		  likely to be "../dejagnu-x.x/dejagnu" if DejaGnu is
		  not installed. If it is installed, it can be invoked
		  as part of your path.
--all		- Print tests that pass and warnings. The default is
		  to only print tests that fail or internal error in
		  DejaGnu. All the test are recorded in the summary
		  file produced by running the tests.
--tool		- This tells DejaGnu which tool you are testing. It is
		  mainly used to find the testsuite directories for a
		  particular tool when several testsuites are in the
		  same directory. (like the GCC and G++ testsuites)
--srcdir	- This points to the top level of the directory
		  containing the sources of the testsuite. This is
		  ./testsuite it you are in the same directory as the
		  README, or if you are in seperate object directory,
		  then it needs to be the path to the testsuite
		  directory. 

	- rob -
	rob@cygnus.com

