URL
https://opencores.org/ocsvn/openrisc/openrisc/trunk
Subversion Repositories openrisc
[/] [openrisc/] [trunk/] [gnu-dev/] [or1k-gcc/] [contrib/] [reghunt/] [examples/] [README] - Rev 723
Compare with Previous | Blame | View Log
This directory contains files from examples of regression hunts, cutdown to smaller ranges to save space and time. Try these out beforeusing the tools on your own tests. First, update gcc-svn-env andcommon.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 fromthe 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 scriptsExamples, where the identifier is the PR number:28970 wrong-code29106 special test, 4.1 branch29578 bogus-warning29906a ice-on-valid-code, break29906b ice-on-valid-code, fix30643 special test, cross compilerCut down the range even further by setting LOW_PATCH and HIGH_PATCHwithin the config file to ids where the log file shows the testpassed or failed.To run one, doreg-hunt 28970.config > 28970.log 2>&1Check on its progress using./reg-watch 28970.logTo run them all, doecho "hunt 28970" > queueecho "hunt 29106" >> queueecho "hunt 29578" >> queueecho "hunt 29906a" >> queueecho "hunt 29906b" >> queueecho "hunt 30643" >> queue./testall queueThis allows you to add more to the queue if you're setting up lots ofhunts.
