Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-105481: do not auto-generate pycore_intrinsics.h#106913
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
bedevere-bot commentedJul 20, 2023
🤖 New build scheduled with the buildbot fleet by@iritkatriel for commitef8c521 🤖 If you want to schedule another build, you need to add the🔨 test-with-refleak-buildbots label again. |
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.
So the process for adding a new intrinsic is now just to add a line to the appropriate table and add a define to pycore_intrinsics.h and update the MAX define there? That's not too tedious.
Some of the refleaks failures look like this:
|
Uh oh!
There was an error while loading.Please reload this page.
pycore_intrinsics.h is currently auto-generated by the build script, which adds complications to the build process but doesn't really buy us anything. This PR defines them in C and exposes through a method in the _opcode module. There are two places where the list of intrinsics is defined before and after this change.