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

Tier 2 superuops #116202

Open
Tracked by #115419
Fidget-Spinner opened this issue Mar 1, 2024 · 0 comments
Open
Tracked by #115419

Tier 2 superuops #116202

Fidget-Spinner opened this issue Mar 1, 2024 · 0 comments
Assignees
Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs) performance Performance or resource usage type-feature A feature request or enhancement

Comments

@Fidget-Spinner
Copy link
Member

Fidget-Spinner commented Mar 1, 2024

Feature or enhancement

Proposal:

Adding superuops at the tier 2 interpreter level should greatly improve the generated code as well.

superuops will need to all share one operand among its constituent uops, and will all need to use only one oparg. This makes it conform to the current instruction format, and not require any changes to the JIT compiler, though it does leave some performance on the table.

Has this already been discussed elsewhere?

No response given

Links to previous discussion of this feature:

No response

Linked PRs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
interpreter-core (Objects, Python, Grammar, and Parser dirs) performance Performance or resource usage type-feature A feature request or enhancement
Projects
None yet
Development

No branches or pull requests

1 participant