Skip to content

Conversation

@davidwrighton
Copy link
Member

  • Detect the case where tail calls are not immediately followed by ret, and fail the tail-call.
  • Detect the attempted usage of tail-calls from within synchronized methods or from within reverse p/invoke methods
  • Use the jit interface canTailCall api when a tail-call is requested
  • Enable tail-calls for calli instructions

Update the TailcallVerifyWithPrefix test to skip tests which depend on the jit performing implicit tail-calls when optimizing when running under the interpreter

This fixes the TailcallVerifyWithPrefix and more_tailcalls test

- Detect the case where tail calls are not immediately followed by ret, and fail the tail-call.
- Detect the attempted usage of tail-calls from within synchronized methods or from within reverse p/invoke methods
- Use the jit interface canTailCall api when a tail-call is requested
- Enable tail-calls for calli instructions

Update the TailcallVerifyWithPrefix test to skip tests which depend on the jit performing implicit tail-calls when optimizing when running under the interpreter

This fixes the TailcallVerifyWithPrefix and more_tailcalls test
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @BrzVlad, @janvorli, @kg
See info in area-owners.md if you want to be subscribed.

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

@davidwrighton davidwrighton merged commit c6af44d into dotnet:main Dec 18, 2025
113 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants