summaryrefslogtreecommitdiff
path: root/unittests/AST
diff options
context:
space:
mode:
authorBen Langmuir <blangmuir@apple.com>2014-05-30 21:20:54 +0000
committerBen Langmuir <blangmuir@apple.com>2014-05-30 21:20:54 +0000
commit9932d9ebb8df6ad6d5f4d81b5dc827eb56bf434d (patch)
tree0244069aa57b43b8a5c283a4bd1aee1cb68ea912 /unittests/AST
parent69d973bb8fff6e0f7d3ce1c7267687884ba7717a (diff)
downloadclang-9932d9ebb8df6ad6d5f4d81b5dc827eb56bf434d.tar.gz
clang-9932d9ebb8df6ad6d5f4d81b5dc827eb56bf434d.tar.bz2
clang-9932d9ebb8df6ad6d5f4d81b5dc827eb56bf434d.tar.xz
Invalidate the file system cache entries for files that may rebuild
This reapplies r209910 with a fix for the assertion failures hit on the buildbots. original commit message: I thought we could get away without this, but it means that the FileEntry objects actually refer to the wrong files, since pcms are not updated inplace, they are atomically renamed into place after compiling a module. So we are close to the original behaviour of invalidating the cache for all modules being removed, but now we should only invalidate the ones that depend on whichever module failed to load. Unfortunately I haven't come up with a new test that didn't require a race between parallel invocations of clang. <rdar://problem/17038180> git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@209922 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'unittests/AST')
0 files changed, 0 insertions, 0 deletions