Skip to content
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

Grand unified tail-calling JIT #129819

Open
Fidget-Spinner opened this issue Feb 7, 2025 · 1 comment
Open

Grand unified tail-calling JIT #129819

Fidget-Spinner opened this issue Feb 7, 2025 · 1 comment
Assignees
Labels
topic-JIT type-feature A feature request or enhancement

Comments

@Fidget-Spinner
Copy link
Member

Fidget-Spinner commented Feb 7, 2025

Feature or enhancement

Proposal:

We have a tail calling interpreter. I now propose to tightly couple that with the JIT, so we can tail call into the JIT and tail call out of it.

This has a few benefits:

  1. No more C stack consumption by the JIT.
  2. Much more efficient entry and exit of jitted code. OSR entry is just a single indirect jump.

We need to align the calling convention of the JIT and the tail calling interpreter. This will need careful benchmarking to make sure we don't regress JIT performance.

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Linked PRs

@Fidget-Spinner Fidget-Spinner added the type-feature A feature request or enhancement label Feb 7, 2025
@Fidget-Spinner Fidget-Spinner self-assigned this Feb 7, 2025
@Fidget-Spinner
Copy link
Member Author

cc @brandtbucher

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic-JIT type-feature A feature request or enhancement
Projects
None yet
Development

No branches or pull requests

1 participant