From: Peter Collingbourne Date: Wed, 15 Feb 2017 03:50:01 +0000 (+0000) Subject: AssumptionCache: Update documentation comment. X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2ece588043fac500b5f305f6e82bf4442538e151;p=llvm AssumptionCache: Update documentation comment. The comment was somewhat misleading in that it implied that passes were not responsible for adding new assumptions to the assumption cache. This new wording now explicitly mentions that they are required to do so. Differential Revision: https://reviews.llvm.org/D29977 git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@295148 91177308-0d34-0410-b5e6-96231b3b80d8 --- diff --git a/include/llvm/Analysis/AssumptionCache.h b/include/llvm/Analysis/AssumptionCache.h index 72c67955a95..bd29292c4c6 100644 --- a/include/llvm/Analysis/AssumptionCache.h +++ b/include/llvm/Analysis/AssumptionCache.h @@ -31,11 +31,10 @@ namespace llvm { /// \brief A cache of @llvm.assume calls within a function. /// /// This cache provides fast lookup of assumptions within a function by caching -/// them and amortizing the cost of scanning for them across all queries. The -/// cache is also conservatively self-updating so that it will never return -/// incorrect results about a function even as the function is being mutated. -/// However, flushing the cache and rebuilding it (or explicitly updating it) -/// may allow it to discover new assumptions. +/// them and amortizing the cost of scanning for them across all queries. Passes +/// that create new assumptions are required to call registerAssumption() to +/// register any new @llvm.assume calls that they create. Deletions of +/// @llvm.assume calls do not require special handling. class AssumptionCache { /// \brief The function for which this cache is handling assumptions. ///