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-106529: Split FOR_ITER_RANGE into uops #106638

Merged
merged 8 commits into from Jul 12, 2023

Conversation

gvanrossum
Copy link
Member

@gvanrossum gvanrossum commented Jul 11, 2023

Ignore the commit history, this is a pile of different experiments.

Benchmark says 1% slower. Now, that's for the version where the "is it exhausted?" check pushes a NULL onto the stack if it is, and the next value if it isn't, which isn't the latest design. So I'm not sure whether I care. If Mark likes the latest version I'll re-run the benchmarks.

(Benchmarking says nothing about the Tier 2 interpreter speed, since that's off except during a few tests.)

@gvanrossum gvanrossum changed the title Split FOR_ITER_RANGE into uops [WIP] gh-106529: Split FOR_ITER_RANGE into uops [WIP] Jul 11, 2023
@gvanrossum gvanrossum changed the title gh-106529: Split FOR_ITER_RANGE into uops [WIP] gh-106529: Split FOR_ITER_RANGE into uops Jul 12, 2023
@gvanrossum gvanrossum marked this pull request as ready for review July 12, 2023 01:46
@gvanrossum
Copy link
Member Author

I will fix the conflict and merge this.

@gvanrossum gvanrossum merged commit dd1884d into python:main Jul 12, 2023
20 checks passed
@gvanrossum gvanrossum deleted the new-for-iter-uops branch July 12, 2023 17:24
@gvanrossum
Copy link
Member Author

New benchmark says it's no faster or slower (in Tier 1, that is). That's good news.

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

2 participants