You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to be able to generate a PCH against one file-system path, and
then re-use that PCH when the file-system path is different (but the
sources are the same). We also do not know when generating the PCH what
the destination file-system path will be, so what we want to be able to
do is:
- When generating a PCH map the original directory to some fake
directory. You could imagine `D:/Foo` being mapped to `Z:/Foo` for
instance.
- Then when consuming a PCH, we want to be able to use a different
mapping to map `Z:/Foo` to `D:/Some/Other/Machines/Foo` for instance.
This will let us generate and share PCHs to speed up compile time for
our users.
To enable this we've made PCH generation respect any specified
vfsoverlay, such that it will remap the paths in the PCH accordingly.
We've also made `-verify-pch` respect the
`-fvalidate-ast-input-files-content` option so that we can force
verification of inputs.
0 commit comments