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

GH-104584: Fix ENTER_EXECUTOR #106141

Merged
merged 5 commits into from Jul 3, 2023

Conversation

markshannon
Copy link
Member

@markshannon markshannon commented Jun 27, 2023

Ensure that the eval-breaker is checked and frame->prev_instr updated before entering executors.

No test changes, or news, as there doesn't seem a way to show that anything is broken.

Copy link
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

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

The block headed by // Equivalent to CHECK_EVAL_BREAKER() in _PyUopExecute() towards the end of ceval.c can now also safely be replaced with a call to CHECK_EVAL_BREAKER().

Python/bytecodes.c Outdated Show resolved Hide resolved
Python/ceval.c Outdated Show resolved Hide resolved
Copy link
Member

@gvanrossum gvanrossum left a comment

Choose a reason for hiding this comment

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

Gotta merge (the dreaded make regen-cases), otherwise LGTM. I could use this for one of my further UOP PRs.

@gvanrossum
Copy link
Member

Can you merge this? Or are you planning to run buildbots first?

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.

None yet

3 participants