-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add explicit null-check for tailcalls to VSD #62719
Conversation
Tagging subscribers to this area: @JulieLeeMSFT Issue DetailsThere is already a comment that this is necessary, but it is only being
|
There is already a comment that this is necessary, but it is only being done for x86 tailcalls via jit helper. Do it for normal tailcalls to VSD as well. Fix dotnet#61486
5debf19
to
da9da5e
Compare
/azp run runtime-coreclr jitstress, runtime-coreclr outerloop |
Azure Pipelines successfully started running 2 pipeline(s). |
For ARM64 this adds 4 bytes to every VSD tail call while on x64 it adds 2 bytes. Diffs showing the size increase. |
Hi! Do you plan to back port this fix to 6.0? |
@k15tfu Yes, I think this is a good candidate for backporting. |
/backport to release/6.0 |
Started backporting to release/6.0: https://github.com/dotnet/runtime/actions/runs/1577668274 |
There is already a comment that this is necessary, but it is only being
done for x86 tailcalls via jit helper. Do it for normal tailcalls to VSD
as well.
Fix #61486