Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
GH-130415: Optimize constant comparison in JIT builds#131489
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
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.
Thanks, this new instruction opens a lot of doors for us in the optimizer! A few things I noticed:
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
When you're done making the requested changes, leave the comment: |
JIT test failure looks unrelated, and due toGH-131488. |
Co-authored-by: Brandt Bucher <brandtbucher@gmail.com>
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.
Just a couple more things. Also, can you merge inmain
? I think JIT CI should be fixed.
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Tail-calling failure is unrelated, and showing up on other PRs too. |
b92ee14
intopython:mainUh oh!
There was an error while loading.Please reload this page.
So next steps would be doing the same thing for the other Is this something you'd be interested in doing? |
Uh oh!
There was an error while loading.Please reload this page.