This is the mail archive of the 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]

Re: Apple's implementation of precompiled headers

Am Die, 2001-10-02 um 21.17 schrieb 1002050270:

> Yes and No,  because how/when to decide if it is 'changed' ?
> -  content is changed


> -  content is same but different compiler options
> -  content is same but different macro settings

Depends on the implementation. When complete "compiled" trees are
serialized this has to be taken into account. Otherwise, when the
macros are evaluated upon compilation, this is irrelevant.

> -  content is same but different time stamp
> -  content is same but different file system location

If you can ensure that the content is the same you can forget about
timestamps and location. But only if....

> Any suggestions ?

I can't think of a good implementation right now to check that the
content hasn't changed or is equal. Well, if the speedadvantage is
expected to come from the avoided parse and compilation process itself
then computing a hash from the headerfiles and storing it in the tree
might be a good idea.


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