This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Problem with PFE approach [Was: Faster compilation speed]
- From: "Timothy J. Wood" <tjw at omnigroup dot com>
- To: dberlin at dberlin dot org
- Cc: jepler at unpythonic dot net, Kai Henningsen <kaih at khms dot westfalen dot de>, <gcc at gcc dot gnu dot org>
- Date: Sun, 18 Aug 2002 14:31:35 -0700
- Subject: Re: Problem with PFE approach [Was: Faster compilation speed]
On Sunday, August 18, 2002, at 01:20 PM, Daniel Berlin wrote:
In other words, you should make sure it works without a PFE header
before you try it *with* one.
This goes back to the issue of user productivity. The whole point of
PFE is to make the development process go faster. You should not have
to take extra steps to validate that your code will get correct
dependancy analysis in order to use a feature that makes the speed of
the compiler usable.
Thus, if you are going to implicitly include the header, you damn
well better included it in dependency analysis. The only way out of
rebuilding everything on a header change, then, is to be able to
automatically figure out which files will be impacted by the changes.
I can accept an argument of "this is too hard to do correctly right
now", but not "the user screwed up". The user didn't screw up -- the
compiler just isn't smart enough to do it correctly yet.
-tim