aboutsummaryrefslogtreecommitdiff
path: root/llvm/lib/Support/Signposts.cpp
diff options
context:
space:
mode:
authorNikita Popov <nikita.ppv@gmail.com>2021-04-03 15:57:58 +0200
committerNikita Popov <nikita.ppv@gmail.com>2021-04-08 22:05:18 +0200
commit59a2f67011ba84a0a72fc97af1ee2bebb2832c16 (patch)
treefe57d97f76eb18dfcacb97052118aa5cc3030cea /llvm/lib/Support/Signposts.cpp
parent189310a140fa1c33f8f4838560f567bab9e99245 (diff)
downloadllvm-59a2f67011ba84a0a72fc97af1ee2bebb2832c16.zip
llvm-59a2f67011ba84a0a72fc97af1ee2bebb2832c16.tar.gz
llvm-59a2f67011ba84a0a72fc97af1ee2bebb2832c16.tar.bz2
[LoopRotate] Don't split loop pass manager
After D99249 we use three different loop pass managers for LICM, LoopRotate and LICM+LoopUnswitch. This happens because LazyBFI and LazyBPI are not preserved by LoopRotate (note that D74640 is no longer needed). Avoid this by marking them as preserved. My understanding of D86156 is that it is okay to simply preserve them (which LoopUnswitch already does for the same reason) and rely on callbacks to deal with deleted blocks. Differential Revision: https://reviews.llvm.org/D99843
Diffstat (limited to 'llvm/lib/Support/Signposts.cpp')
0 files changed, 0 insertions, 0 deletions