-
-
Notifications
You must be signed in to change notification settings - Fork 31.9k
gh-115778: Add a tierN
annotation for instruction definition
#115815
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
Conversation
Eclips4
commented
Feb 22, 2024
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: Bytecodes cleanup: promote TIER_{ONE,TWO}_ONLY to properties #115778
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.
Looks like a nice improvement. Thanks.
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.
Basically LG, though I have two nits:
- If there ever is a Tier 3, I expect that several of the tier checks will have to be adjusted -- currently there seems to be an assumption that if it's not T1 then it's T2 and vice versa.
- Inferring tier 1 from specialized could be done differently.
Co-authored-by: Alex Waygood <[email protected]>
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.
Thanks!
@gvanrossum |
Thanks! |
…ython#115815) This replaces the old `TIER_{ONE,TWO}_ONLY` macros. Note that `specialized` implies `tier1`. Co-authored-by: Alex Waygood <[email protected]>
…ython#115815) This replaces the old `TIER_{ONE,TWO}_ONLY` macros. Note that `specialized` implies `tier1`. Co-authored-by: Alex Waygood <[email protected]>
…ython#115815) This replaces the old `TIER_{ONE,TWO}_ONLY` macros. Note that `specialized` implies `tier1`. Co-authored-by: Alex Waygood <[email protected]>