This is the mail archive of the
mailing list for the GCC project.
Re: gcc compile-time performance
- From: dewar at gnat dot com (Robert Dewar)
- To: dewar at gnat dot com, jss at ast dot cam dot ac dot uk
- Cc: gcc at gcc dot gnu dot org
- Date: Sat, 18 May 2002 09:29:24 -0400 (EDT)
- Subject: Re: gcc compile-time performance
> I'd just be nice for gcc to be faster if that wasn't too hard to do! Maybe
> precompiled headers would make a significant difference. Perhaps gcc
> developers would like to get gcc's internals in a better state before
> going down this line.
It seems to me that if precompiled headers would make a huge difference, then
they are patching a synmptom which is that the C++ front end is too slow.
The issue of fancy new optimizations is something that basically affects
the back end, and there are fundamental reasons why you would expect the
GCC back end to be slower than backends aimed at specific architectures
But there is no reason for the g++ front end to be slower than for example
the Code Warrior front end. If code warrior can do a complete C++ compile
in 2 minutes, then for sure the g++ front end need not take longer than this.
On the other hand a full C++ front end is a very complex beast, so this is
not something that can be casually fixed.
Mark, you were working on a new g++ parser, what's the story on that