aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/CodeGen/MachineFunction.cpp
diff options
context:
space:
mode:
authorArthur Eubanks <aeubanks@google.com>2020-12-28 09:27:28 -0800
committerArthur Eubanks <aeubanks@google.com>2020-12-28 10:38:51 -0800
commit9abc457724bd54014328a6f0b7ed230bacd9f610 (patch)
tree56eaecc68e0602eb35db39079874c49858a0ee7b /llvm/lib/CodeGen/MachineFunction.cpp
parent7b00e9fae3853d4693e608cc52f6d6da5059f5ff (diff)
downloadllvm-9abc457724bd54014328a6f0b7ed230bacd9f610.zip
llvm-9abc457724bd54014328a6f0b7ed230bacd9f610.tar.gz
llvm-9abc457724bd54014328a6f0b7ed230bacd9f610.tar.bz2
[NewPM][AMDGPU] Port amdgpu-simplifylib/amdgpu-usenative
And add them to the pipeline via AMDGPUTargetMachine::registerPassBuilderCallbacks(), which mirrors AMDGPUTargetMachine::adjustPassManager(). These passes can't be unconditionally added to PassRegistry.def since they are only present when the AMDGPU backend is enabled. And there are no target-specific headers in llvm/include, so parsing these pass names must occur somewhere in the AMDGPU directory. I decided the best place was inside the TargetMachine, since the PassBuilder invokes TargetMachine::registerPassBuilderCallbacks() anyway. If we come up with a cleaner solution for target-specific passes in the future that's fine, but there aren't too many target-specific IR passes living in target-specific directories so it shouldn't be too bad to change in the future. Reviewed By: ychen, arsenm Differential Revision: https://reviews.llvm.org/D93863
Diffstat (limited to 'llvm/lib/CodeGen/MachineFunction.cpp')
0 files changed, 0 insertions, 0 deletions