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.
GH-133231: Changes to executor management to support proposed
sys._jit
module #133287New 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
GH-133231: Changes to executor management to support proposed
sys._jit
module #133287Changes from all commits
3a2ccda
46ef280
01ecf18
89e4668
2f42cb0
f938d68
a30e444
0b9dcb7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Side note, this instruction now exists solely to set the
current_executor
in the tier two interpreter. We should try to remove it as a follow-up (doesn't need to be in this PR).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can replace all uses of
current_executor
with an operand, which will remove thecurrent_executor
local variable from the tier 2 interpreter and the_JIT_EXECUTOR
patch from the JIT template.We can also shrink
_CHECK_VALIDITY
a bit by replacingcurrent_executor->vm_data.valid
with*validity_ptr
:For another PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this needed? We only need one slot in
localsplus
, which_PyInterpreterFrame
already has.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We now need two slots. One on the stack for the return value, as before, and one local variable to hold the current executor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see. Forgot about the return value.
Maybe add a comment that the one stack slot is for the return value, and the one local is for the executor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor: this seems redundant, given that we're setting it one line above.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.