Allow implicit widenings when tailcalling#54864
Merged
jakobbotsch merged 2 commits intodotnet:mainfrom Jul 5, 2021
Merged
Conversation
The managed calling convention dictates that the callee is responsible for widening up to 4 bytes. We can use this to allow some more tailcalls. Fix dotnet#51957
jakobbotsch
commented
Jun 28, 2021
| // is tracked with https://github.com/dotnet/runtime/issues/8413. | ||
| // | ||
| // 3) If the callee has a 9 to 16 byte struct argument and the callee has | ||
| // If the callee has a 9 to 16 byte struct argument and the callee has |
Member
Author
There was a problem hiding this comment.
This comment was outdated, both of the issues have been fixed.
Member
Author
|
/azp run runtime-coreclr jitstress, runtime-coreclr outerloop |
|
Azure Pipelines successfully started running 2 pipeline(s). |
Member
Author
|
PTAL @dotnet/jit-contrib |
Member
|
Are failed jitstress jobs related? |
EgorBo
approved these changes
Jul 5, 2021
Member
Member
Author
I believe the failing test is #54200
Hmm, looks like it. I can try to take a look at that separately. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.

The managed calling convention dictates that the callee is responsible
for widening up to 4 bytes. We can use this to allow some more
tailcalls.
Fix #51957
I couldn't use SPMI as the new tailcalls change the jitinterface calls (thanks for explaining @sandreenko), so I used PMI. A few diffs in frameworks:
Diffs look as expected, we get some cases where we were relying on the widening anyway.
cc @dotnet/jit-contrib