This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC testsuite timeout question (gcc.c-torture/compile/20001226-1.c)
- From: Steve Ellcey <sje at cup dot hp dot com>
- To: ebotcazou at libertysurf dot fr
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 31 Aug 2005 10:55:51 -0700 (PDT)
- Subject: Re: GCC testsuite timeout question (gcc.c-torture/compile/20001226-1.c)
> > By hand, I can compile the test in about 3 1/2 minutes on the machine in
> > question (the machine may have been busier when the failure occured and thus
> > taken longer).
>
> I think it's a real regression (memory consumption/speed) of the compiler, it
> is timing out on all the slow SPARC machines I have (it is OK with 4.0.x).
> IIRC I observed the same regression between 3.2.x and 3.3.x on even slower
> machines, but 3.4.x fixed it.
>
> --
> Eric Botcazou
Yes, I think you are right. I can see a substantial slowdown in
compilation times on IA64 HP-UX at -O2 (though it doesn't time out
there).
gcc 4.0.0 - 81 seconds
gcc 3.4.1 - 38 seconds
gcc 3.4.0 - 37 seconds
gcc 3.3.5 - 89 seconds
gcc 3.3.1 - 91 seconds
3.3 is slow, 3.4 is faster, 4.0.0 seems slow agin, I don't have 4.0.*
hanging around to test.
Looking at a timing report based on the 4.0.0 compiler it looks like
half the compile time is spent in the phase "dominance frontiers".
I will investigate some more.
Steve Ellcey
sje@cup.hp.com