1*4fee23f9SmrgThis directory contains scripts that are used by the regression 2*4fee23f9Smrgtester, <http://gcc.gnu.org/regtest/> 3*4fee23f9Smrg 4*4fee23f9SmrgThe primary script is 'btest-gcc.sh'. This is the script that is run 5*4fee23f9Smrgto actually test the compiler. 6*4fee23f9Smrg 7*4fee23f9Smrg'objs-gcc.sh' takes a combined tree and builds (but does not test) the 8*4fee23f9Smrgtools required for 'btest-gcc.sh'. It is run periodically to update 9*4fee23f9Smrgthe tools. This script is followed by running 'btest-gcc.sh' using 10*4fee23f9Smrgthe newly-build tools to check that they will not cause regressions. 11*4fee23f9Smrg 12*4fee23f9Smrg'site.exp' is what $DEJAGNU points to when the regression tester runs 13*4fee23f9Smrgthese scripts. 14*4fee23f9Smrg 15*4fee23f9Smrg'GCC_Regression_Tester.wdgt' is a Dashboard widget that displays the 16*4fee23f9Smrgcurrent state of the tester using Javascript. You can use it without 17*4fee23f9Smrgneeding Dashboard by pointing your web browser at 18*4fee23f9Smrg'GCC_Regression_Tester.wdgt/widget.html', if your browser supports 19*4fee23f9Smrgand permits it. 20*4fee23f9Smrg 21*4fee23f9SmrgNote that any changes made here need to be approved by the regression 22*4fee23f9Smrgtester's maintainer (see MAINTAINERS). The changes will be used on 23*4fee23f9Smrgthe tester's next run, so `experimental' changes are very strongly 24*4fee23f9Smrgdiscouraged :-). 25