compile time testsuite [Re: alias slowdown?]

[Janis Johnson]

On Tue, Nov 21, 2006 at 02:59:12PM -0000, Dave Korn wrote:
> On 21 November 2006 13:54, Benjamin Kosnik wrote:
> 
> 
> > My suggestion would be to check in
> >
> > all.i
> > bug2.ii
> > cpgram.ii
> >
> > And whatever stuff there is for measuring slowdowns, and then create
> > an optional "make check-compile" rule for gcc/Makefile that runs
> > through the tests. I believe that you will have to make this testing
> > always optional, since there will no doubt be pathological behavior
> > involved.
> >
> > Then you could do
> >
> > time make check-compile
> >
> > And get a better picture of what's up. I'm sure there are other ways
> > of doing this (better?), and I'd be interested in hearing them.
> 
>   We already have a suitable mechanism, there's no need to trouble with a new
> top-level make target.  Just add a time-compile.exp script and use
> RUNTESTFLAGS to specify it if you want to run it on its own.

There are already at least a couple of sets of tests that are at least
partially optional.  gcc.test-framework/test-framework.exp tests are
skipped unless CHECK_TEST_FRAMEWORK is defined, and skip the
time-consuming generated tests unless CHECK_TEST_FRAMEWORK is 1.
gcc.dg/compat/struct-layout-1.exp generates and runs lots of additional
tests if RUN_ALL_COMPAT_TESTS is defined.

There's no need to add an additional make target, or to do a separate
run specifying the .exp file, just run the tests whenever an environment
variable is defined.

Janis