Uh oh!
There was an error while loading. Please reload this page.
JIT: Disallow parameters passed in float regs from being enregistered in int regs - #99286
Conversation
Just verifying that we never see float reg -> int reg homing on all our targets...
ghost
commented
Mar 5, 2024
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch Issue DetailsJust verifying that we never see float reg -> int reg homing on all our targets...
|
jakobbotsch
commented
Mar 7, 2024
/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress, runtime-coreclr jitstressregs, runtime-coreclr libraries-jitstressregs |
jakobbotsch
commented
Mar 7, 2024
/azp run runtime-coreclr jitstress, runtime-coreclr libraries-jitstress, runtime-coreclr jitstressregs, runtime-coreclr libraries-jitstressregs |
|
Azure Pipelines successfully started running 4 pipeline(s). |
jakobbotsch
commented
Mar 7, 2024
cc @dotnet/jit-contrib PTAL @BruceForstall This change is a follow-up to #96439. The logic in that PR is only correct under the assumption that parameters passed in float regs are never homed in integer regs. However, we can enregister structs of fitting size in integer registers if they have only whole uses, so that could still happen for a struct passed in float registers. This is a very rare case because such enregistration only kicks in when the struct parameter also was not promoted. The right long term fix here is to generalize |
See #99286 (comment).