This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem with PFE approach [Was: Faster compilation speed]


On Friday, August 16, 2002, at 02:41 PM, Neil Booth wrote:

Devang Patel wrote:-

In your previous two queries, what you want from PFE is to discard few
things
based on macros from precompiled headers. But when PFE restores trees,
it has gone too far as far as macros are concerned.
The implementation should know what its assumptions are, and if they're
broken recover somehow.  Have you seen KAI's documentation (online)
for their PCH implementation?  It seems like a good solution to me.
I saw it when we started working on PFE. We have followed MW like
approach in PFE. PFE can be modified to be like KAI's implementation.

But, I think, KAI implementation is concentrated on precompilling headers only.
From beginning, one of the requirement of PFE is to be able to save
and restore already compiled sources, provide debugging information and
make available central repository of saved trees for feedback and
inter-modular optimizations. To achieve this larger goal, it was
decided that an external tool like IDE can handle other issues like what to
include in prefix header. Because, in PFE it is not just prefix header, but it is
a prefix file.

(BTW I have never used MW, so I may be absolutely wrong
that PFE is like MW)

-Devang


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]