summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorReid Kleckner <rnk@google.com>2015-11-02 20:47:31 +0000
committerReid Kleckner <rnk@google.com>2015-11-02 20:47:31 +0000
commitf7e61478df6fed6c5768ef37e82ddf11650a15e5 (patch)
tree56f1fde3b5b33d499ad677f10c2b5faa8d2f363f
parent746426b48727a9850b0c58b135d2934616b909b0 (diff)
downloadbcm5719-llvm-f7e61478df6fed6c5768ef37e82ddf11650a15e5.tar.gz
bcm5719-llvm-f7e61478df6fed6c5768ef37e82ddf11650a15e5.zip
[PTH] Fix data length used for stat cache entries
This came up in a boost build, which apparently uses PTH. This was broken in r187619 when we migrated it to uses llvm::fs instead of raw stat calls. Constructing a test case with a hash table collision in-tree is tough. Instead, I have a pending change to OnDiskChainedHashTable that asserts that the reported length of the data agrees with the data actually written. All of the existing in-tree tests find the bug with this assert. llvm-svn: 251828
-rw-r--r--clang/lib/Frontend/CacheTokens.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/clang/lib/Frontend/CacheTokens.cpp b/clang/lib/Frontend/CacheTokens.cpp
index 662778b7a65..87f3d172581 100644
--- a/clang/lib/Frontend/CacheTokens.cpp
+++ b/clang/lib/Frontend/CacheTokens.cpp
@@ -106,7 +106,7 @@ public:
}
unsigned getRepresentationLength() const {
- return Kind == IsNoExist ? 0 : 4 + 4 + 2 + 8 + 8;
+ return Kind == IsNoExist ? 0 : 4 * 8;
}
};
OpenPOWER on IntegriCloud