From 554fd8c5195424bdbcabf5de30fdc183aba391bd Mon Sep 17 00:00:00 2001 From: upstream source tree Date: Sun, 15 Mar 2015 20:14:05 -0400 Subject: obtained gcc-4.6.4.tar.bz2 from upstream website; verified gcc-4.6.4.tar.bz2.sig; imported gcc-4.6.4 source tree from verified upstream tarball. downloading a git-generated archive based on the 'upstream' tag should provide you with a source tree that is binary identical to the one extracted from the above tarball. if you have obtained the source via the command 'git clone', however, do note that line-endings of files in your working directory might differ from line-endings of the respective files in the upstream repository. --- contrib/reghunt/examples/README | 53 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 contrib/reghunt/examples/README (limited to 'contrib/reghunt/examples/README') diff --git a/contrib/reghunt/examples/README b/contrib/reghunt/examples/README new file mode 100644 index 000000000..ebf1bcb9b --- /dev/null +++ b/contrib/reghunt/examples/README @@ -0,0 +1,53 @@ +This directory contains files from examples of regression hunts, cut +down to smaller ranges to save space and time. Try these out before +using the tools on your own tests. First, update gcc-svn-env and +common.config for your own environment. + +Each of the examples has multiple files: + + *.list files were created using gcc-svn-patchlist + + *.config files were written by hand based on earlier config files; + the commented-out pieces are left as templates in case they're needed + + *.c, *.c++ are source files for the test, usually taken directly from + the PR + + *.test files are tests specific to a bug when an existing gcc-test-* + script can't be used + + *.log files are output from various scripts + +Examples, where the identifier is the PR number: + + 28970 wrong-code + 29106 special test, 4.1 branch + 29578 bogus-warning + 29906a ice-on-valid-code, break + 29906b ice-on-valid-code, fix + 30643 special test, cross compiler + +Cut down the range even further by setting LOW_PATCH and HIGH_PATCH +within the config file to ids where the log file shows the test +passed or failed. + +To run one, do + + reg-hunt 28970.config > 28970.log 2>&1 + +Check on its progress using + + ./reg-watch 28970.log + +To run them all, do + + echo "hunt 28970" > queue + echo "hunt 29106" >> queue + echo "hunt 29578" >> queue + echo "hunt 29906a" >> queue + echo "hunt 29906b" >> queue + echo "hunt 30643" >> queue + ./testall queue + +This allows you to add more to the queue if you're setting up lots of +hunts. -- cgit v1.2.3