This is the mail archive of the
mailing list for the GCC project.
Re: Faster compilation speed
- From: Dale Johannesen <dalej at apple dot com>
- To: Aaron Lehmann <aaronl at vitelus dot com>
- Cc: Dale Johannesen <dalej at apple dot com>, Mike Stump <mrs at apple dot com>, gcc at gcc dot gnu dot org
- Date: Mon, 12 Aug 2002 10:36:53 -0700
- Subject: Re: Faster compilation speed
On Saturday, August 10, 2002, at 05:48 PM, Aaron Lehmann wrote:
On Fri, Aug 09, 2002 at 12:17:32PM -0700, Mike Stump wrote:
I'd like to introduce lots of various changes to improve compiler
Just adding my two cents to the discussion - I saw many ideas
presented in this thread that look promising, but one thing that I
didn't see mentioned was gcc's extensive sanity checking. There are
many tests which will produce an internal compiler error when merited.
This is great tool for debugging, but most of these errors should be
impossible to reach. Does anyone know how much overhead this sanity
checking in general causes, and whether there are any sanity checks
that are unusually expensive and should be considered for removal?
Many compilers conditionalize these checks with #if DEBUG or the like.
I hesitate to recommend this, as bugs that show up in the non-checked
version of the compiler can be baffling, but it's worth mentioning.
Profile-based code straightening is a big win on code like this, but that
doesn't get rid of the test, of course.