2002-02-02 06:23:34 +01:00
|
|
|
This directory contains scripts that are used by the regression
|
2004-11-07 18:08:09 +01:00
|
|
|
tester, <http://gcc.gnu.org/regtest/>
|
2002-02-02 06:23:34 +01:00
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
2005-11-23 21:29:09 +01:00
|
|
|
'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%20Regression%20Tester.wdgt/widget.html', if your browser supports
|
|
|
|
|
and permits it.
|
|
|
|
|
|
2002-02-02 06:23:34 +01:00
|
|
|
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 :-).
|
