|Compiler stress tests? email@example.com (1997-01-02)|
|Re: Compiler stress tests? firstname.lastname@example.org (Duane Sand) (1997-01-03)|
|Re: Compiler stress tests? email@example.com (1997-01-03)|
|Re: Compiler stress tests? firstname.lastname@example.org (1997-01-04)|
|Re: Compiler stress tests? email@example.com (1997-01-12)|
|Re: Compiler stress tests? firstname.lastname@example.org (1997-01-16)|
|Re: Compiler stress tests? email@example.com (Stephen Baynes) (1997-01-17)|
|Re: Compiler stress tests? firstname.lastname@example.org (John Haxby) (1997-01-22)|
|From:||email@example.com (Cliff Click)|
|Date:||3 Jan 1997 23:07:13 -0500|
firstname.lastname@example.org (David Keppel) writes:
> Somebody asked me about this and I don't know the answer: where do you
> find compiler "stress test" generators/suites/etc.? ...
> [I'd look at mechanically generated source code, since it always seems to
> kill compilers expecting human-written code. -John]
I work for the Motorola compiler group. We use PlumHall (C, C++,
Fortran), Spec92, Spec95, Nullstone, Linpack, Stanford Integer
Benchmark and Bytemarks (did I miss any?). We make regression tests
for any bug that makes it into the bug reporting system - especially
bugs that come from external users. The regression suite is (I think)
several thousand cases long. We run the whole shebang on every minor
In short, we throw the kitchen sink at the compiler.
Beta testers still find bugs with amazing ease.
Cliff Click, Ph.D. Compiler Researcher & Designer
RISC Software, Motorola PowerPC Compilers
email@example.com (512) 891-7240
Return to the
Search the comp.compilers archives again.