Consistently use FunctionAnalysisManager
Besides a general consistently benefit, the extra layer of indirection allows the mechanical part of https://reviews.llvm.org/D23256 that requires touching every transformation and analysis to be factored out cleanly. Thanks to David for the suggestion. llvm-svn: 278077
This commit is contained in:
@@ -2031,7 +2031,7 @@ INITIALIZE_PASS_END(LoopAccessLegacyAnalysis, LAA_NAME, laa_name, false, true)
|
||||
char LoopAccessAnalysis::PassID;
|
||||
|
||||
LoopAccessInfo LoopAccessAnalysis::run(Loop &L, AnalysisManager<Loop> &AM) {
|
||||
const AnalysisManager<Function> &FAM =
|
||||
const FunctionAnalysisManager &FAM =
|
||||
AM.getResult<FunctionAnalysisManagerLoopProxy>(L).getManager();
|
||||
Function &F = *L.getHeader()->getParent();
|
||||
auto *SE = FAM.getCachedResult<ScalarEvolutionAnalysis>(F);
|
||||
|
||||
Reference in New Issue
Block a user