Ensure that the new merge BB (which contains the rest of the original BB
after the mem op being optimized) gets a profile frequency, in case
there are additional mem ops later in the BB. Otherwise they get skipped
as the merge BB looks cold.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
lib/Transforms/Instrumentation/IndirectCallPromotion.cpp | ||
---|---|---|
955 ↗ | (On Diff #96435) | This comment seems unnecessary :) Also can you move the DefaultBB setting after MergeBB update? |
lib/Transforms/Instrumentation/IndirectCallPromotion.cpp | ||
---|---|---|
955 ↗ | (On Diff #96435) | Sure. I mostly added the comment to indicate why it was important to update the MergeBB profile frequency specifically (and not the other new BBs), but can remove it. |