Re: Compilers QA

"Joachim Durchholz" <joachim_d@gmx.de>
18 Jul 2001 19:56:42 -0400

          From comp.compilers
Related articles
Compilers QA ori@grapesys.com (Ori Idan) (2001-07-03)
Re: Compilers QA marcov@toad.stack.nl (2001-07-06)
Re: Compilers QA tej@melbpc.org.au (Tim Josling) (2001-07-17)
Re: Compilers QA joachim_d@gmx.de (Joachim Durchholz) (2001-07-18)
Re: Compilers QA ralph@inputplus.demon.co.uk (2001-07-23)
Re: Compilers QA ppluzhnikov@earthlink.net (Paul Pluzhnikov) (2001-07-23)
Re: Compilers QA ralph@inputplus.demon.co.uk (2001-07-23)
| List of all articles for this month |
From: "Joachim Durchholz" <joachim_d@gmx.de>
Newsgroups: comp.compilers
Date: 18 Jul 2001 19:56:42 -0400
Organization: Compilers Central
References: 01-07-037 01-07-059
Keywords: testing
Posted-Date: 18 Jul 2001 19:56:42 EDT

Tim Josling <tej@melbpc.org.au> wrote:
>
> Throw as much real live test input as you can find, from
> different sources. Real users will do many unbelievable things.
> 'Why would you want to do that?' is the question you will be
> asking.


Oh, and if you can, write some code generators that stress test the
compiler. Things that I have seen break compilers are:
* Variable names of several K length
* Several hundred levels of nesting
    * Statement nesting
    * Expression nesting
* Several thousand cases in switch statements


All of this can and does appear in automatically generated code, so
these tests should be somewhere in your test plan.


Regards,
Joachim

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.