Hi Tejas, On Wed, Jun 12 2019, Tejas Joshi wrote: > Hello. > Is this the correct sequence for regression test: > 1. Revert back all the changes I made and then configure, build along with > make bootstrap > make -k check > collect the *.sum files > 2. Apply the patch and do the configuration, build as above 1 and then > collect the *.sum files and compare them.
Yes, exactly (make sure to pass an appropriate -j parameter to make, of course). > > How do I collect and inspect these *.sum files? I collect *.sum files with a small script that internally simply does cp -vp `find . -name '*.sum' -print` $DEST_DIRECTORY with different $DEST_DIR for pristine trunk and the patched version. I admit I have my own script for comparing *.sum files but the usual way is to use the compare_tests in the contrib directory, so for comparing the old and new gcc.sum, you would do something like: ./src/contrib/compare_tests ../trunk/logs/gcc.sum logs/gcc.sum with the directories matching your setup, of course. Writing about scripts in contrib, you might also want to look at check_GNU_style.sh and/or check_GNU_style.py. They take a patch file as they argument and check GNU style (things like two spaces after each sentence, long lines, these tiny things where we still however try to be consistent). Of course, some of the errors given should be ignored, in your case probably long lines in a *.def file. Hope this helps, Martin
