Searched refs:MemoryDependenceAnalysis (Results 1 – 20 of 20) sorted by relevance
513 class MemoryDependenceAnalysis514 : public AnalysisInfoMixin<MemoryDependenceAnalysis> {515 friend AnalysisInfoMixin<MemoryDependenceAnalysis>;524 MemoryDependenceAnalysis();525 …MemoryDependenceAnalysis(unsigned DefaultBlockScanLimit) : DefaultBlockScanLimit(DefaultBlockScanL… in MemoryDependenceAnalysis() function
82 MemoryDependenceAnalysis.cpp \
90 "MemoryDependenceAnalysis.cpp",
101 MemoryDependenceAnalysis.cpp
1719 AnalysisKey MemoryDependenceAnalysis::Key;1721 MemoryDependenceAnalysis::MemoryDependenceAnalysis() in MemoryDependenceAnalysis() function in MemoryDependenceAnalysis1725 MemoryDependenceAnalysis::run(Function &F, FunctionAnalysisManager &AM) { in run()1765 auto PAC = PA.getChecker<MemoryDependenceAnalysis>(); in invalidate()
13 ``MemoryDependenceAnalysis`` for most (if not all) use-cases. This is because,14 unless you're very careful, use of ``MemoryDependenceAnalysis`` can easily16 have as many arbitrary limits as ``MemoryDependenceAnalysis``, so you should get
432 Using the ``MemoryDependenceAnalysis`` Pass681 ``MemoryDependenceAnalysis`` to :doc:`MemorySSA`. Please try to use
230 FUNCTION_ANALYSIS("memdep", MemoryDependenceAnalysis())
1243 MemoryDependenceResults &MD = AM.getResult<MemoryDependenceAnalysis>(F); in run()
752 isMemDepEnabled() ? &AM.getResult<MemoryDependenceAnalysis>(F) : nullptr; in run()
1144 ./usr/include/llvm/Analysis/MemoryDependenceAnalysis.h
1143 ./usr/include/llvm/Analysis/MemoryDependenceAnalysis.h
1145 ./usr/include/llvm/Analysis/MemoryDependenceAnalysis.h