OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
b2ed63b4aa
gcc/contrib/regression
History
Andrew Pinski c8db7d5c17 btest-gcc.sh: gcc.sum has moved to gcc/testsuite/gcc/gcc.sum. 
2006-01-18  Andrew Pinski  <pinskia@physics.uc.edu>

        * btest-gcc.sh: gcc.sum has moved to gcc/testsuite/gcc/gcc.sum.
        g++.sum has moved to gcc/testsuite/g++/g++.sum.
        objc.sum has moved to gcc/testsuite/objc/objc.sum.

From-SVN: r109937
2006-01-18 17:09:56 -08:00
..
GCC_Regression_Tester.wdgt GCC Regression Tester.wdgt: Rename to GCC_Regression_Tester.wdgt. 2005-11-28 17:41:07 +00:00
btest-gcc.sh btest-gcc.sh: gcc.sum has moved to gcc/testsuite/gcc/gcc.sum. 2006-01-18 17:09:56 -08:00
ChangeLog btest-gcc.sh: gcc.sum has moved to gcc/testsuite/gcc/gcc.sum. 2006-01-18 17:09:56 -08:00
objs-gcc.sh All files: Update with new FSF address. 2005-08-15 00:41:31 +00:00
README GCC Regression Tester.wdgt: Rename to GCC_Regression_Tester.wdgt. 2005-11-28 17:41:07 +00:00
site.exp btest-gcc.sh: For crosses, assume newlib and GNU binutils. 2002-03-09 19:41:11 +00:00

README 

This directory contains scripts that are used by the regression
tester, <http://gcc.gnu.org/regtest/>

The primary script is 'btest-gcc.sh'.  This is the script that is run
to actually test the compiler.

'objs-gcc.sh' takes a combined tree and builds (but does not test) the
tools required for 'btest-gcc.sh'.  It is run periodically to update
the tools.  This script is followed by running 'btest-gcc.sh' using
the newly-build tools to check that they will not cause regressions.

'site.exp' is what $DEJAGNU points to when the regression tester runs
these scripts.

'GCC_Regression_Tester.wdgt' is a Dashboard widget that displays the
current state of the tester using Javascript.  You can use it without
needing Dashboard by pointing your web browser at
'GCC_Regression_Tester.wdgt/widget.html', if your browser supports
and permits it.

Note that any changes made here need to be approved by the regression
tester's maintainer (see MAINTAINERS).  The changes will be used on
the tester's next run, so `experimental' changes are very strongly
discouraged :-).