Testing GCC 2.95 with the current testsuite

For the upcoming GCC 2.95.3 release, we need to perform tests on as many platforms as possible to make sure we have no regressions from the previous release. We need volunteers to do these tests. This document is an attempt to provide a step-by-step walkthrough of what needs to be done.

You may want to read the general instructions for testing first. These describe some steps necessary to set up the infrastructure needed to run the testsuite at all.

Once you have done that, proceed with these steps:

1. Download gcc-2.95.2 and the current testsuite:
   gcc-2.95.2.tar.gz
   gcc-tests-20001127.tar.gz

2. Extract both, then move the testsuite into the right place:

   rm -rf gcc-2.95.2/gcc/testsuite
mv gcc-20001127/gcc/testsuite gcc-2.95.2/gcc/

3. Change into the directory "gcc-2.95.2/gcc/testsuite" and apply this patch as follows:

   patch -p0 <testsuite.diff

4. Build the 2.95.2 release on all available targets (using "make bootstrap").

5. Run the testsuite ("make -k check"), and send in the results. There's a script, "gcc-2.95.2/contrib/test_summary", which will apparently help you postprocess those results into a usable form. If you run it like this (while in the toplevel build directory)

   gcc-2.95.2/contrib/test_summary | sh

   it will automatically mail the results to the right place.

The same thing will then have to be done for the 2.95.3 test releases which ought to start appearing shortly after Dec 17, 2000. If you want, you can already do tests on the current branch; the CVS branch tag is "gcc-2_95-branch". Don't forget to substitute the new testsuite on the branch as well.