Re: 3.2.2 & 3.3 branch & trunk compilation speed comparison (MICO)

[Devang Patel <dpatel at apple dot com>]

On Wednesday, February 12, 2003, at 05:49 AM, Karel Gardas wrote:

> Now I would like to find the best methodology how to make testing of 
> gcc
> branches for compile-time regressions.
That would be very useful.

> 1) daily or weekly?
daily is better :-)

> 2) on whole tree or choose some/one file(s)?
> 4) anyway which files might be 'interesting'?
Select few files from your test project. Since your project is C++,
I would say
- One source file which uses STL
- One source file which does not (or very little) use STL
- One large source file like ir.cc
- One small source file

> 3) would you like to see -ftime-report -fmem-report for some 
> interesting
>    files?
Only if delta is large enough to notice.

> 5) which branch(es) to test?
Main trunk (3.4) and next release branch (3.3)

> 6) which optimization levels - i.e. I tested only what's the most
>    important for development when I try to make compilation time as 
> short
>    as possible, by turn off all optimizations...?
Yes, speed without optimization is important right now.

> 7) anything other which should I test for you?
>
> Thanks a lot for your time,
> Karel
Thank you,

-Devang