Am 03.07.2012 12:23 schrieb "JC Chu" <jc...@acm.org>: > > On Tue, Jul 3, 2012 at 3:55 PM, Sven Barth <pascaldra...@googlemail.com> wrote: > > I don't know whether you know this, but: > > * testing the compiler compilation (as a first step) is best done using > > "make cycle" in the compiler subdirectory (optionally "make fullcycle" if > > you changed something were a subset of the supported platforms is affected) > > I did “make compiler” in $(source)\compiler and copied the resulting > executable to my scratch directory. No wonder I didn’t find out the > error. (ಠ_ಠ)
Now you know a better way :) > > * if the compiler can be compiled you should do a "make clean all > > TEST_FPC=path/to/your/newly/compiled/ppcXXX" in the "tests" directory and > > compare with a testrun of the same version without the modifications (it's > > sufficient to copy the "log" or "faillist" file from the > > "tests/output/yourcpu-youros" directory for comparison) > > Could you elaborate on that? Do I need to run the test suite with the > old compiler first? * first do a "make cycle" on a unmodified checkout, then run the testsuite. * save the "log" and/or "faillog" file * do your modifications (might involve some "make cycle" executions until you're satisfied with the results) * run the testsuite again and compare the new "log" or "faillist" file against the backuped counterpart * if there are no explainable changes in succeeding/failing tests: publish your patch * otherwise correct your changes so that you don't introduce regressions and repeat at point 4 Regards, Sven
_______________________________________________ fpc-pascal maillist - fpc-pascal@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-pascal
