This is the mail archive of the
mailing list for the GCC project.
RE: Faster Compliations - PCH support?
- From: "Robert McNulty Junior" <bmj2001 at bellsouth dot net>
- To: "Shawn Starr" <spstarr at sh0n dot net>,"Neil Booth" <neil at daikokuya dot co dot uk>
- Cc: "Andrew Pinski" <pinskia at physics dot uc dot edu>,<gcc at gcc dot gnu dot org>
- Date: Sun, 11 Aug 2002 16:40:33 -0500
- Subject: RE: Faster Compliations - PCH support?
Does'nt Microsoft Visual C++ have this built-in?
From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of
Sent: Sunday, August 11, 2002 4:19 PM
To: Neil Booth
Cc: Andrew Pinski; email@example.com
Subject: Re: Faster Compliations - PCH support?
I was thinking PCH was generating p-code (bytecode) for header files to be
used when compiling sources.
On Sun, 11 Aug 2002, Neil Booth wrote:
> Andrew Pinski wrote:-
> > Read the archives, there are a few different PCH support for gcc
> > and one or a combination might be added to gcc.
> > Also it is not the preprocessing that takes a long time but the
> > parsing that takes the longest time on c++.
> > So it might be faster to change the parsing code which is
> > ongoing, look at the cp-parse branch.
> I think you misunderstand the scope of PCH. PCH does a lot more
> than preprocessing; it tends to combine all of preprocessing,
> parsing, decl creation, type layout, semantic checks and possibly
> even more into one. Ideally it would represent all compiler state
> up to the point where the main file's real code begins.
Shawn Starr, sh0n.net, <firstname.lastname@example.org>
Maintainer: -shawn kernel patches: http://xfs.sh0n.net/2.4/
Software Engineer, Open Source Development