This is the mail archive of the
mailing list for the GCC project.
Re: gcc compile-time performance
- From: Gabriel Dos Reis <gdr at codesourcery dot com>
- To: dewar at gnat dot com (Robert Dewar)
- Cc: jss at ast dot cam dot ac dot uk, gcc at gcc dot gnu dot org
- Date: 18 May 2002 16:06:00 +0200
- Subject: Re: gcc compile-time performance
- Organization: CodeSourcery, LLC
- References: <20020518132924.E6F40F2A59@nile.gnat.com>
email@example.com (Robert Dewar) writes:
| > 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.
That is just restatement of evidences people have been reporting for
quite a long time.
I don't think it is reasonable to tell them to buy faster computers,
even if that seems an easier answer.
| 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
| for example.
| But there is no reason for the g++ front end to be slower than for example
| the Code Warrior front end.
Sure there is a reason: g++ front-end architecture.