This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: C++ compile time (again)
- From: Diego Novillo <dnovillo at redhat dot com>
- To: Karel Gardas <kgardas at objectsecurity dot com>
- Cc: Wolfgang Bangerth <bangerth at ices dot utexas dot edu>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: 13 Jun 2003 11:50:39 -0400
- Subject: Re: C++ compile time (again)
- Organization: Red Hat Canada
- References: <Pine.LNX.4.43.0306131727580.26402-100000@thinkpad.c0202001.roe.itnq.net>
On Fri, 2003-06-13 at 11:41, Karel Gardas wrote:
> On Fri, 13 Jun 2003, Wolfgang Bangerth wrote:
>
> > It's C++-compile-time-regression-rant time again. Compile times for a
> > complete build of the deal.II library on a PIII 800 MHz:
> >
> > gcc2.95 : 46 min
> > mainline: 89 min
> > tree-ssa: 118 min
>
> Looks very similar for MICO too, although I haven't tested tree-ssa yet,
> should I?
>
Yes, please. We need all the data we can get. If you can run it every
day, then great. Otherwise, send me a couple of pointers and I'll add
it to the list.
> (note: in whole email I will talk about compiler performance with using
> -O0 only)
>
I've had a notion of enabling some very simplistic cleanups at -O0. But
it's down there at the bottom of the list.
> Does anybody here have anything like that? (just to not reinvent a wheel)
>
You could try using my SPEC scripts. I want to pretend they're simple
to modify for things other than SPEC. But they're written in bash, what
a dreadful scripting language that is. Let me know if you're
interested.
Diego.