Related articles |
---|
Unit testing a compiler dido@imperium.ph (Rafael R. Sevilla) (2013-03-13) |
Re: Unit testing a compiler cr88192@hotmail.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 walter@bytecraft.com (Walter Banks) (2013-03-19) |
From: | Walter Banks <walter@bytecraft.com> |
Newsgroups: | comp.compilers |
Date: | Tue, 19 Mar 2013 18:02:54 -0500 |
Organization: | A noiseless patient Spider |
References: | 13-03-009 |
Keywords: | debug |
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.
w..
Return to the
comp.compilers page.
Search the
comp.compilers archives again.