aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineScheduler.cpp
diff options
context:
space:
mode:
authorWhitney Tsang <whitneyt@ca.ibm.com>2020-12-16 17:05:44 +0000
committerWhitney Tsang <whitneyt@ca.ibm.com>2020-12-16 17:07:14 +0000
commitfa3693ad0b34ef1d64f49e3d3dd10865b9fb7a8b (patch)
treed9ca0c08bf042473ea2e7fbbbee52152bf9de71f /llvm/lib/CodeGen/MachineScheduler.cpp
parentc0619d3b21cd420b9faf15f14db0816787c44ded (diff)
downloadllvm-fa3693ad0b34ef1d64f49e3d3dd10865b9fb7a8b.zip
llvm-fa3693ad0b34ef1d64f49e3d3dd10865b9fb7a8b.tar.gz
llvm-fa3693ad0b34ef1d64f49e3d3dd10865b9fb7a8b.tar.bz2
[LoopNest] Handle loop-nest passes in LoopPassManager
Per http://llvm.org/OpenProjects.html#llvm_loopnest, the goal of this patch (and other following patches) is to create facilities that allow implementing loop nest passes that run on top-level loop nests for the New Pass Manager. This patch extends the functionality of LoopPassManager to handle loop-nest passes by specializing the definition of LoopPassManager that accepts both kinds of passes in addPass. Only loop passes are executed if L is not a top-level one, and both kinds of passes are executed if L is top-level. Currently, loop nest passes should have the following run method: PreservedAnalyses run(LoopNest &, LoopAnalysisManager &, LoopStandardAnalysisResults &, LPMUpdater &); Reviewed By: Whitney, ychen Differential Revision: https://reviews.llvm.org/D87045
Diffstat (limited to 'llvm/lib/CodeGen/MachineScheduler.cpp')
0 files changed, 0 insertions, 0 deletions