|compiler/translator testing techniques email@example.com (Ruslan Vorobey) (2003-03-30)|
|Re: compiler/translator testing techniques firstname.lastname@example.org (Christopher Glaeser) (2003-03-30)|
|Re: compiler/translator testing techniques email@example.com (Ruslan Vorobey) (2003-03-31)|
|Re: compiler/translator testing techniques firstname.lastname@example.org (Scott Moore) (2003-04-05)|
|Re: compiler/translator testing techniques email@example.com (Christopher Glaeser) (2003-04-05)|
|From:||"Ruslan Vorobey" <firstname.lastname@example.org>|
|Date:||31 Mar 2003 13:40:52 -0500|
|Posted-Date:||31 Mar 2003 13:40:52 EST|
"Christopher Glaeser" <email@example.com> wrote in message
> > Can anybody point me to links/books regarding compiler/translator
> > testing methods, techniques etc?
> For a link to compiler performance testing, see http://www.nullstone.com
> [If you're serious about testing, it's a lot cheaper to buy a serious
> test suite from a company like Nullstone than to try to concoct your
> own. -John]
Thank you for link, I'll investigate it.
The question concerned not really performance (but it also very
important) but approaches to verify ready compiler created with
lex/yacc pair or fully custom how it conform to customer's
requirements. Really technique to create testing environments,
testcases, what should be tested first etc.
I think this question to people with some experience in creating
Return to the
Search the comp.compilers archives again.