aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/FileOutputBuffer.cpp
diff options
context:
space:
mode:
authorBen Langmuir <blangmuir@apple.com>2014-05-30 17:42:15 +0000
committerBen Langmuir <blangmuir@apple.com>2014-05-30 17:42:15 +0000
commit04b9c70da6be729bd828f0d3e41b91b945591814 (patch)
tree7aa28382a48b102a7eb6965810992b5f9209ee3a /llvm/lib/Support/FileOutputBuffer.cpp
parent897f23dda82cae6e08c464509195be90015ed3c8 (diff)
downloadllvm-04b9c70da6be729bd828f0d3e41b91b945591814.zip
llvm-04b9c70da6be729bd828f0d3e41b91b945591814.tar.gz
llvm-04b9c70da6be729bd828f0d3e41b91b945591814.tar.bz2
Invalidate the file system cache entries for files that may rebuild
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: 209910
Diffstat (limited to 'llvm/lib/Support/FileOutputBuffer.cpp')
0 files changed, 0 insertions, 0 deletions