mirror of
https://github.com/RPCS3/llvm-mirror.git
synced 2024-11-25 12:12:47 +01:00
[ThinLTO] Also prune Thin-* files from the ThinLTO cache
Such files (Thin-%%%%%%.tmp.o) are supposed to be deleted immediately after they're used (either by renaming or deletion). However, we've seen instances on Windows where this doesn't happen, probably due to the filesystem being flaky. This is effectively a resource leak which has prevented us from using the ThinLTO cache on Windows. Since those temporary files are in the thinlto cache directory which we prune periodically anyway, allowing them to be pruned too seems like a tidy way to solve the problem. Differential revision: https://reviews.llvm.org/D94962
This commit is contained in:
parent
3496691e63
commit
12b7677de1
@ -211,11 +211,12 @@ bool llvm::pruneCache(StringRef Path, CachePruningPolicy Policy) {
|
||||
// Walk all of the files within this directory.
|
||||
for (sys::fs::directory_iterator File(CachePathNative, EC), FileEnd;
|
||||
File != FileEnd && !EC; File.increment(EC)) {
|
||||
// Ignore any files not beginning with the string "llvmcache-". This
|
||||
// Ignore filenames not beginning with "llvmcache-" or "Thin-". This
|
||||
// includes the timestamp file as well as any files created by the user.
|
||||
// This acts as a safeguard against data loss if the user specifies the
|
||||
// wrong directory as their cache directory.
|
||||
if (!sys::path::filename(File->path()).startswith("llvmcache-"))
|
||||
StringRef filename = sys::path::filename(File->path());
|
||||
if (!filename.startswith("llvmcache-") && !filename.startswith("Thin-"))
|
||||
continue;
|
||||
|
||||
// Look at this file. If we can't stat it, there's nothing interesting
|
||||
|
Loading…
Reference in New Issue
Block a user