-
-
Notifications
You must be signed in to change notification settings - Fork 31k
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-111485: Mark some instructions as TIER_ONE_ONLY
#113155
Conversation
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.
LGTM
Maybe eventually the tier-one-only marker could be one of the instruction attributes (like |
Yeah, I would like that too. The less we need to poke around in the token soup (and keep things in the DSL header) the better. |
Go for it!
…On Fri, Dec 15, 2023 at 11:47 AM Brandt Bucher ***@***.***> wrote:
Yeah, I would like that too.
The less we need to poke around in the token soup (and keep things in the
DSL header) the better.
—
Reply to this email directly, view it on GitHub
<#113155 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAWCWMXFPDXFMBTNGONY7T3YJSSLTAVCNFSM6AAAAABAWA4SYGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYGQYDMOJUGA>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
--
--Guido van Rossum (python.org/~guido)
|
Recent refactoring has made it so that the interpreter generator is now emitting executor cases for some instructions that were implicitly non-viable as uops before. This marks those instructions as explicitly
TIER_ONE_ONLY
.