a1b78fb929
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
25 lines
582 B
LLVM
25 lines
582 B
LLVM
; RUN: opt -debug-only=branch-prob -passes="require<branch-prob>,jump-threading" -S %s 2>&1 | FileCheck %s
|
|
; RUN: opt -debug-only=branch-prob -passes=jump-threading -S %s 2>&1 | FileCheck %s --check-prefix=CHECK-NOBPI
|
|
; REQUIRES: asserts
|
|
|
|
; Make sure that we clear edge probabilities for bb1 as we fold
|
|
; the conditional branch in it.
|
|
|
|
; CHECK: eraseBlock bb1
|
|
; CHECK-NOBPI-NOT: eraseBlock bb1
|
|
|
|
define i32 @foo() !prof !0 {
|
|
; CHECK-LABEL: @foo
|
|
bb1:
|
|
br i1 true, label %bb2, label %bb3
|
|
|
|
bb2:
|
|
ret i32 3
|
|
|
|
bb3:
|
|
; CHECK-NOT: bb3:
|
|
ret i32 7
|
|
}
|
|
|
|
!0 = !{!"function_entry_count", i64 0}
|