Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.7k
gh-98831: Modernize CALL_FUNCTION_EX#101627
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
Uh oh!
There was an error while loading.Please reload this page.
gvanrossum commentedFeb 7, 2023
On top of that the tests fail. Going back into draft mode. |
Also avoid compiler warning for unused variable 'null'(used in assert only).
10dcbec to19307baComparebedevere-bot commentedFeb 7, 2023
🤖 New build scheduled with the buildbot fleet by@gvanrossum for commit19307ba 🤖 If you want to schedule another build, you need to add the |
gvanrossum commentedFeb 7, 2023
@iritkatriel Crash fixed, warning fixed, tests passed, refleak buildbots are running. Ready for your review. |
gvanrossum commentedFeb 8, 2023
I'm taking the PPC64LE RHEL8 Refleaks PR buildbot failure as a flake. |
Uh oh!
There was an error while loading.Please reload this page.
This is a straightforward use of a conditional input stack effect. The one tricky bit is that I had to cherry-pick a fix for CHECK_EVAL_BREAKER() fromgh-101508. Whichever lands first, the other will have to drop that commit.