README
1This directory contains files from examples of regression hunts, cut
2down to smaller ranges to save space and time. Try these out before
3using the tools on your own tests. First, update gcc-svn-env and
4common.config for your own environment.
5
6Each of the examples has multiple files:
7
8 *.list files were created using gcc-svn-patchlist
9
10 *.config files were written by hand based on earlier config files;
11 the commented-out pieces are left as templates in case they're needed
12
13 *.c, *.c++ are source files for the test, usually taken directly from
14 the PR
15
16 *.test files are tests specific to a bug when an existing gcc-test-*
17 script can't be used
18
19 *.log files are output from various scripts
20
21Examples, where the identifier is the PR number:
22
23 28970 wrong-code
24 29106 special test, 4.1 branch
25 29578 bogus-warning
26 29906a ice-on-valid-code, break
27 29906b ice-on-valid-code, fix
28 30643 special test, cross compiler
29
30Cut down the range even further by setting LOW_PATCH and HIGH_PATCH
31within the config file to ids where the log file shows the test
32passed or failed.
33
34To run one, do
35
36 reg-hunt 28970.config > 28970.log 2>&1
37
38Check on its progress using
39
40 ./reg-watch 28970.log
41
42To run them all, do
43
44 echo "hunt 28970" > queue
45 echo "hunt 29106" >> queue
46 echo "hunt 29578" >> queue
47 echo "hunt 29906a" >> queue
48 echo "hunt 29906b" >> queue
49 echo "hunt 30643" >> queue
50 ./testall queue
51
52This allows you to add more to the queue if you're setting up lots of
53hunts.
54