Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.compilers > #876
| From | Walter Banks <walter@bytecraft.com> |
|---|---|
| Newsgroups | comp.compilers |
| Subject | Re: Unit testing a compiler |
| Date | 2013-03-19 18:02 -0500 |
| Organization | A noiseless patient Spider |
| Message-ID | <13-03-015@comp.compilers> (permalink) |
| References | <13-03-009@comp.compilers> |
"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..
Back to comp.compilers | Previous | Next — Previous in thread | Find similar | Unroll thread
Unit testing a compiler "Rafael R. Sevilla" <dido@imperium.ph> - 2013-03-13 11:50 +0800 Re: Unit testing a compiler BGB <cr88192@hotmail.com> - 2013-03-13 02:59 -0500 Re: Unit testing a compiler Robert A Duff <bobduff@shell01.TheWorld.com> - 2013-03-13 18:58 -0400 Re: Unit testing a compiler Walter Banks <walter@bytecraft.com> - 2013-03-19 18:02 -0500
csiph-web