-
-
Notifications
You must be signed in to change notification settings - Fork 31.1k
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
GH-128563: Simplify recursion check in _PyEval_EvalFrameDefault
#129481
GH-128563: Simplify recursion check in _PyEval_EvalFrameDefault
#129481
Conversation
markshannon
commented
Jan 30, 2025
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: A new tail-calling interpreter for significantly better interpreter performance #128563
@@ -786,7 +786,11 @@ _PyEval_EvalFrameDefault(PyThreadState *tstate, _PyInterpreterFrame *frame, int | |||
|
|||
_PyInterpreterFrame entry_frame; | |||
|
|||
|
|||
if (_Py_EnterRecursiveCallTstate(tstate, "")) { | |||
assert(frame->owner != FRAME_OWNED_BY_INTERPRETER); |
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.
Don't you need to _Py_LeaveRecursiveCallPy
after this as well?
At least from reading the code of exit_unwind
.
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.
No. We haven't called _Py_EnterRecursivePy
When you're done making the requested changes, leave the comment: |
I have made the requested changes; please review again |
Thanks for making the requested changes! @Fidget-Spinner: please review the changes made to this pull request. |
…meDefault` (pythonGH-129481)" This reverts commit c3ae5c9.
…t` (pythonGH-129481) Simplify recursion check in _PyEval_EvalFrameDefault