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]



So, another problem with PFE that I've noticed after working with it for a while...

If you put all your commonly used headers in a PFE, then changing any of these headers causes the PFE header to considered changed. And, since this header is imported into every single file in your project, you end up in a situation where changing any header causes the entire project to be rebuilt. This is clearly not good for day to day development.

A PCH approach that was automatic and didn't have a single monolithic file would avoid the artificial tying together of all the headers in the world and would thus lead to faster incremental builds due to fewer files being rebuilt.

Another approach that would work with a monolithic file would be some sort of fact database that would allow the build system to decide early on that the change in question didn't effect some subset of files.

-tim


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