diff options
author | Dan Albert <danalbert@google.com> | 2016-02-04 18:51:25 +0000 |
---|---|---|
committer | Gerrit Code Review <noreply-gerritcodereview@google.com> | 2016-02-04 18:51:25 +0000 |
commit | edbbe53c4ffa154a5f9ae3f89ba8105993d8800e (patch) | |
tree | 4cedb380a14027d9c4d1e531c2340c43cbd79175 /gcc-4.8.1/contrib/regression/README | |
parent | a4ca82cac69c3147143d7b4b4d7cdeb5e02f20ef (diff) | |
parent | 3186be22b6598fbd467b126347d1c7f48ccb7f71 (diff) | |
download | toolchain_gcc-edbbe53c4ffa154a5f9ae3f89ba8105993d8800e.tar.gz toolchain_gcc-edbbe53c4ffa154a5f9ae3f89ba8105993d8800e.tar.bz2 toolchain_gcc-edbbe53c4ffa154a5f9ae3f89ba8105993d8800e.zip |
Merge "Check in a pristine copy of GCC 4.8.1."
Diffstat (limited to 'gcc-4.8.1/contrib/regression/README')
-rw-r--r-- | gcc-4.8.1/contrib/regression/README | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/gcc-4.8.1/contrib/regression/README b/gcc-4.8.1/contrib/regression/README new file mode 100644 index 000000000..9e94e5c39 --- /dev/null +++ b/gcc-4.8.1/contrib/regression/README @@ -0,0 +1,24 @@ +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 :-). |