aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineModuleInfo.cpp
diff options
context:
space:
mode:
authorArthur Eubanks <aeubanks@google.com>2020-12-14 18:06:10 -0800
committerArthur Eubanks <aeubanks@google.com>2020-12-21 13:46:07 -0800
commit76f4f42ebaf9146da3603943bea7c52ca58ae692 (patch)
tree91bbca4eebc67e86637578f36b61418a8eddd194 /llvm/lib/CodeGen/MachineModuleInfo.cpp
parentffba47df76460905965df4b54cf6ba945d2eb1ce (diff)
downloadllvm-76f4f42ebaf9146da3603943bea7c52ca58ae692.zip
llvm-76f4f42ebaf9146da3603943bea7c52ca58ae692.tar.gz
llvm-76f4f42ebaf9146da3603943bea7c52ca58ae692.tar.bz2
[NewPM] Add TargetMachine method to add alias analyses
AMDGPUTargetMachine::adjustPassManager() adds some alias analyses to the legacy PM. We need a way to do the same for the new PM in order to port AMDGPUTargetMachine::adjustPassManager() to the new PM. Currently the new PM adds alias analyses by creating an AAManager via PassBuilder and overriding the AAManager a PassManager uses via FunctionAnalysisManager::registerPass(). We will continue to respect a custom AA pipeline that specifies an exact AA pipeline to use, but for "default" we will now add alias analyses that backends specify. Most uses of PassManager use the "default" AAManager created by PassBuilder::buildDefaultAAPipeline(). Backends can override the newly added TargetMachine::registerAliasAnalyses() to add custom alias analyses. Reviewed By: ychen Differential Revision: https://reviews.llvm.org/D93261
Diffstat (limited to 'llvm/lib/CodeGen/MachineModuleInfo.cpp')
0 files changed, 0 insertions, 0 deletions