|Unit testing a compiler firstname.lastname@example.org (Rafael R. Sevilla) (2013-03-13)|
|Re: Unit testing a compiler email@example.com (BGB) (2013-03-13)|
|Re: Unit testing a compiler bobduff@shell01.TheWorld.com (Robert A Duff) (2013-03-13)|
|Re: Unit testing a compiler firstname.lastname@example.org (Walter Banks) (2013-03-19)|
|From:||Walter Banks <email@example.com>|
|Date:||Tue, 19 Mar 2013 18:02:54 -0500|
|Organization:||A noiseless patient Spider|
|Posted-Date:||22 Mar 2013 10:35:24 EDT|
"Rafael R. Sevilla" wrote:
> I am currently writing a simple byte compiler for a simple dialect of
> Lisp, and am wondering what is the best practice for testing such a
> compiler. ...
My compiler regression tests are run through a simulator and a report
generated for each test of go/nogo for compile/link and correct
execution as well as code size, ram requirements and execution time
output in a cvs file. This can then be added to a progress summary
spreadsheet to track progress.
Return to the
Search the comp.compilers archives again.