aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/FileOutputBuffer.cpp
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
commit4f05478c9729a00e61757b7842099f0e1db988e8 (patch)
tree42d87bebe435ab4c5b4b1c63e49061f82a16d862 /llvm/lib/Support/FileOutputBuffer.cpp
parent357e5e9cafbd2ea7999415067df42e85938c80c7 (diff)
downloadllvm-4f05478c9729a00e61757b7842099f0e1db988e8.zip
llvm-4f05478c9729a00e61757b7842099f0e1db988e8.tar.gz
llvm-4f05478c9729a00e61757b7842099f0e1db988e8.tar.bz2
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> llvm-svn: 209922
Diffstat (limited to 'llvm/lib/Support/FileOutputBuffer.cpp')
0 files changed, 0 insertions, 0 deletions