forked from OSchip/llvm-project
f96ea53e89
getModRefInfo() queries currently track whether the result is a MustAlias on a best-effort basis. The only user of this functionality is the optimized memory access type in MemorySSA -- which in turn has no users. Given that this functionality has not found a user since it was introduced five years ago (in D38862), I think we should drop it again. The context is that I'm working to separate FunctionModRefBehavior to track mod/ref for different location kinds (like argmem or inaccessiblemem) separately, and the fact that ModRefInfo also has an unrelated Must flag makes this quite awkward, especially as this means that NoModRef is not a zero value. If we want to retain the functionality, I would probably split getModRefInfo() results into a part that just contains the ModRef information, and a separate part containing a (best-effort) AliasResult. Differential Revision: https://reviews.llvm.org/D130713 |
||
|---|---|---|
| .. | ||
| AliasSet | ||
| AssumptionCache | ||
| BasicAA | ||
| BlockFrequencyInfo | ||
| BranchProbabilityInfo | ||
| CFLAliasAnalysis | ||
| CallGraph | ||
| CostModel | ||
| CycleInfo | ||
| DDG | ||
| Delinearization | ||
| DemandedBits | ||
| DependenceAnalysis | ||
| DivergenceAnalysis | ||
| DominanceFrontier | ||
| Dominators | ||
| FunctionPropertiesAnalysis | ||
| GlobalsModRef | ||
| IRSimilarityIdentifier | ||
| IVUsers | ||
| LazyCallGraph | ||
| LazyValueAnalysis | ||
| LegacyDivergenceAnalysis | ||
| Lint | ||
| LoopAccessAnalysis | ||
| LoopCacheAnalysis | ||
| LoopInfo | ||
| LoopNestAnalysis | ||
| MemoryDependenceAnalysis | ||
| MemorySSA | ||
| MustExecute | ||
| PhiValues | ||
| PostDominators | ||
| ProfileSummary | ||
| RegionInfo | ||
| ScalarEvolution | ||
| ScopedNoAliasAA | ||
| StackSafetyAnalysis | ||
| TypeBasedAliasAnalysis | ||
| ValueTracking | ||
| alias-analysis-uses.ll | ||