ARM32: stop allocating a register for null checks on instance calls #68100
Conversation
For interface tail calls we currently end up allocating two internal registers where one of them is forced into R12. LSRA currently does not always handle the low amount of freedom, in particular with some jitstressregs scenarios. Since LR is always free going into a call we can just stop allocating a register for the null check and use LR always to avoid the problem and also give LSRA a little less work to do. Fix dotnet#66563
dotnet-issue-labeler
bot
added
the
area-CodeGen-coreclr
|
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsFor interface tail calls we currently end up allocating two internal Since LR is always free going into a call we can just stop allocating a Fix #66563 cc @dotnet/jit-contrib
|
|
This reasoning is right only for tailcalls since for regular calls we could have allocated the target into |
|
Replaced by #68107 |
ghost
locked as resolved and limited conversation to collaborators
For interface tail calls we currently end up allocating two internal
registers where one of them is forced into R12. LSRA currently does not
always handle the low amount of freedom, in particular with some
jitstressregs scenarios.
Since LR is always free going into a call we can just stop allocating a
register for the null check and use LR always to avoid the problem and
also give LSRA a little less work to do.
Fix #66563
cc @dotnet/jit-contrib