This is the mail archive of the
mailing list for the GCC project.
Re: Apple's PFE for GCC is now available
- From: Alex Hornby <alex at anvil dot co dot uk>
- To: Stan Shebs <shebs at apple dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: 01 Aug 2002 09:58:40 +0100
- Subject: Re: Apple's PFE for GCC is now available
- References: <3D476BEF.email@example.com>
On Wed, 2002-07-31 at 05:47, Stan Shebs wrote:
> Last year, I posted a message describing Apple's Persistent Front End
> (PFE) project (http://gcc.gnu.org/ml/gcc/2001-09/msg01210.html). I'm
> now pleased to announce that the complete source code is now both
> available and portable; it runs well on GNU/Linux, and likely other
> types of systems as well.
> When used to implement precompiled headers, PFE offers a considerable
> speedup; typically 6x for 100KLoc Mac headers, and as much as 12x on
> Linux using comparable synthetic headers. (Of course, your results
> will vary considerably, depending on everything from system RAM to
> source file size.) PFE has been in production use for building
> parts of Jaguar for some months now, so it's known to be reliable.
As a GCC user, would I need to restructure my project's includes to
benefit from PFE?
The reason I ask is that some pch implementations I've used (e.g.
borland's) seem to require a "one big header" approach with a pch header
that includes all the other headers. This means that if you change one
header file everything ends up rebuilding, which obviously negates some
of the build speedup benefits. Of course perhaps I'm just using the
borland pch incorrectly :)