Skip to content

GH-108614: Remove TIER_ONE and TIER_TWO from _PUSH_FRAME #108725

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

Merged
merged 3 commits into from
Sep 4, 2023

Conversation

markshannon
Copy link
Member

@markshannon markshannon commented Aug 31, 2023

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.

LGTM. I like how you managed to remove the HAS_ERROR flag from three uops!

@gvanrossum
Copy link
Member

Running the tests while forcing -Xuops shows a leak: https://github.com/python/cpython/actions/runs/6042493339/job/16397717979?pr=107820

Though this might be due to another recent PR too.

@markshannon
Copy link
Member Author

Have you tested for leaks on main?
I don't see any obvious places where this would introduce a leak.

@markshannon markshannon changed the title GH-108614: Remove TIER_ONE and TIER_TWO from _PUSH_FRAME`` GH-108614: Remove TIER_ONE and TIER_TWO from _PUSH_FRAME Sep 1, 2023
@gvanrossum
Copy link
Member

Good call, it looks on main too with -Xuops. So go ahead and merge.

@markshannon markshannon merged commit 5a3672c into python:main Sep 4, 2023
@markshannon markshannon deleted the remove-tiers-push-frame branch September 5, 2023 12:25
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.

3 participants