diff options
author | Evgeniy Brevnov <ybrevnov@azul.com> | 2022-11-25 17:29:27 +0700 |
---|---|---|
committer | Evgeniy Brevnov <ybrevnov@azul.com> | 2023-01-27 15:00:16 +0700 |
commit | 26e7cb24cb5dfa560683064d37f560558f00aa67 (patch) | |
tree | 26863ee264beabaf16f9be74b159471f4038411e /llvm/lib/CodeGen/StackProtector.cpp | |
parent | 7b966e2156b8b461a29a49122286f804a30236e9 (diff) | |
download | llvm-26e7cb24cb5dfa560683064d37f560558f00aa67.zip llvm-26e7cb24cb5dfa560683064d37f560558f00aa67.tar.gz llvm-26e7cb24cb5dfa560683064d37f560558f00aa67.tar.bz2 |
[JT][CT] Preserve exisiting BPI/BFI during JumpThreading
Currently, JT creates and updates local instances of BPI\BFI. As a result global ones have to be invalidated if JT made any changes.
In fact, JT doesn't use any information from BPI/BFI for the sake of the transformation itself. It only creates BPI/BFI to keep them up to date. But since it updates local copies (besides cases when it updates profile metadata) it just waste of time.
Current patch is a rework of D124439. D124439 makes one step and replaces local copies with global ones retrieved through AnalysisPassManager. Here we do one more step and don't create BPI/BFI if the only reason of creation is to keep BPI/BFI up to date. Overall logic is the following. If there is cached BPI/BFI then update it along the transformations. If there is no existing BPI/BFI, then create it only if it is required to update profile metadata.
Please note if BPI/BFI exists on exit from JT (either cached or created) it is always up to date and no reason to invalidate it.
Reviewed By: mkazantsev
Differential Revision: https://reviews.llvm.org/D136827
Diffstat (limited to 'llvm/lib/CodeGen/StackProtector.cpp')
0 files changed, 0 insertions, 0 deletions