Re: compile time testsuite [Re: alias slowdown?]

["Richard Guenther" <richard dot guenther at gmail dot com>]

On 11/21/06, Benjamin Kosnik <bkoz@redhat.com> wrote:
> > Perhaps we need a webpage with multiple compile times being tracked,
> > or simply a standard compile time regression suite from existing PRs
> > to avoid this kind of thing in the future.
>
> I think it is past time for a formal compile-time testsuite.
>
> 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.

Public monitoring would be more useful.  If you have working single-file
testcases that you want be monitored for compile-time and memory-usage
just contact me and I can add them to the daily tester
(http://www.suse.de/~gcctest/c++bench/).

And I believe Honza may be interested to put them to the memory-tester as well.

Richard.