Based on an off-list discussion, I’ve updated this patch to not check for 
configuration mismatches (e.g. different langopts), since checking for 
staleness is the interesting case to check for and adding all the requisite 
langopts to the command line increases the complexity of using the feature.

Ben

Attachment: verify-pch.patch
Description: Binary data


On Jan 21, 2014, at 8:18 PM, Ben Langmuir <[email protected]> wrote:

> 
>> Looks good!
>> Could you also add a driver option (maybe "--verify-pch") ?
> 
> Sure, I’ve added -verify-pch to the driver as well.  I kept the same spelling 
> between the two options.  The biggest change here is that we don’t want the 
> driver to pass through -x TYPE to cc1 for an input file that is a pch when we 
> are verifying, since we want to verify the *source* language.  Right now I am 
> omitting "-x TYPE" when -verify-pch is set AND the input file has a .pch 
> extension.  I’m not sure whether checking the extension is a good idea, but 
> it is consistent with other bits of the compiler that will assume the input 
> is an object file if it has no extension and no explicit -x option.  I’m 
> happy to change it.
> 
> Ben
> 
> <verify-pch.patch>
> 
> 
> _______________________________________________
> cfe-commits mailing list
> [email protected]
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

_______________________________________________
cfe-commits mailing list
[email protected]
http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits

Reply via email to