Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED!nerds-end From: Walter Banks Newsgroups: comp.compilers Subject: Re: Unit testing a compiler Date: Tue, 19 Mar 2013 18:02:54 -0500 Organization: A noiseless patient Spider Lines: 14 Sender: johnl@iecc.com Approved: comp.compilers@iecc.com Message-ID: <13-03-015@comp.compilers> References: <13-03-009@comp.compilers> NNTP-Posting-Host: news.iecc.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: leila.iecc.com 1363962925 93552 64.57.183.58 (22 Mar 2013 14:35:25 GMT) X-Complaints-To: abuse@iecc.com NNTP-Posting-Date: Fri, 22 Mar 2013 14:35:25 +0000 (UTC) Keywords: debug Posted-Date: 22 Mar 2013 10:35:24 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:876 "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..