doc: add guide on how to add a bytecode specialization (#1286) - #1900
doc: add guide on how to add a bytecode specialization (#1286)#1900nayanraj864-cmyk wants to merge 2 commits into
Conversation
|
All commit authors signed the Contributor License Agreement. |
for more information, see https://pre-commit.ci
Documentation build overview
|
|
@Fidget-Spinner My name is Nayan Raj, and I have recently started contributing to organizations that participate in Google Summer of Code (GSoC). This is my first experience contributing to a GSoC organization, although I have previously worked on other open-source projects and have some contribution experience. I would greatly appreciate any guidance, suggestions, or feedback that could help me improve my contributions and better understand the GSoC contribution process. I am eager to learn, enhance my skills, and become a valuable contributor to the community. Thank you for your time and support. I look forward to learning from your experience and contributing effectively to the project. Best regards, |
|
IMO this does not belong in the devguide, but instead in the InternalDocs. It relies on specific internals that are subject to change across versions. |
2 participants
This PR adds a comprehensive guide detailing how to introduce a new bytecode specialization in CPython.
Changes Included:
developer-workflow/bytecode-specialization.rst: Added a 9-step guide covering opcode modifications (bytecodes.c), specializing micro-ops (uop), macro definitions, cache structs (pycore_code.h), specializing functions (specialize.c), execution stats, disassembler cache layout (Lib/opcode.py), magic number bumping (pycore_magic_number.h), and code regeneration.developer-workflow/index.rst: Registeredbytecode-specializationin the sectiontoctree.index.rst: Linked the new guide in the Code column on the main Devguide homepage navigation table.Closes #1286