[BOLT][RISCV] Handle long tail calls #67098
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Long tail calls use the following instruction sequence on RISC-V:
Since the second instruction in isolation looks like an indirect branch, this confused BOLT and most functions containing a long tail call got marked with "unknown control flow" and didn't get optimized as a consequence.
This patch fixes this by detecting long tail call sequence in
analyzeIndirectBranch
.FixRISCVCallsPass
also had to be updated to expand long tail calls toPseudoTAIL
instead ofPseudoCALL
.Besides this, this patch also fixes a minor issue with compressed tail calls (
c.jr
) not being detected.Note that I had to change
BinaryFunction::postProcessIndirectBranches
slightly: the documentation ofMCPlusBuilder::analyzeIndirectBranch
mentions that the [Begin
,End
) range contains the instructions immediately precedingInstruction
. However, inpostProcessIndirectBranches
, all the instructions in the BB where passed in the range. This made it difficult to find the preceding instruction so I made sure only the preceding instructions are passed.