Dec 6, 2024 · Nov 22, 2024 · Nov 22, 2024 · Nov 23, 2024 · Nov 28, 2024 · Dec 5, 2024
diff --git a/InternalDocs/code_objects.md b/InternalDocs/code_objects.md
 although they are often written to disk by one process and read back in by another.
 The disk version of a code object is serialized using the
 [marshal](https://docs.python.org/dev/library/marshal.html) protocol.
 When a[`CodeObject`](code_objects.md) is created, the function
 `_PyCode_Quicken()` from[`Python/specialize.c`](../Python/specialize.c) is
 called to initializethe caches of all adaptive instructions. This is
 required because theon-disk format is a sequence of bytes, and
 some of the caches need to beinitialized with 16-bit values.
 When a `CodeObject` is created, the function `_PyCode_Quicken()` from
 [`Python/specialize.c`](../Python/specialize.c) is called to initialize
 the caches of all adaptive instructions. This is required because the
 on-disk format is a sequence of bytes, and some of the caches need to be
 initialized with 16-bit values.

 Code objects are nominally immutable.
 Some fields (including `co_code_adaptive` and fields for runtime
diff --git a/InternalDocs/interpreter.md b/InternalDocs/interpreter.md
 ## Families of instructions

 A *family* of instructions consists of an adaptive instruction along with the
 specializedinstruction that it can be replaced by.
 specializedinstructions that it can be replaced by.
 It has the following fundamental properties:

 * It corresponds to a single instruction in the code
diff --git a/InternalDocs/jit.md b/InternalDocs/jit.md
 When the full jit is enabled (python was configured with
 [`--enable-experimental-jit`](https://docs.python.org/dev/using/configure.html#cmdoption-enable-experimental-jit),
 the uop executor's `jit_code` field is populated with a pointer to a compiled
 C function thatimplement the executor logic. This function's signature is
 C function thatimplements the executor logic. This function's signature is
 defined by `jit_func` in [`pycore_jit.h`](Include/internal/pycore_jit.h).
 When the executor is invoked by `ENTER_EXECUTOR`, instead of jumping to
 the uop interpreter at `tier2_dispatch`, the executor runs the function
 the jitted code is constructed for an executor by
 [`_PyJIT_Compile`](../Python/jit.c).

 The stencils are generated under thebuild target `regen-jit` by the scripts
 in [`/Tools/jit`](/Tools/jit). This script reads
 The stencils are generatedat build timeunder theMakefile target `regen-jit`
 by the scriptsin [`/Tools/jit`](/Tools/jit). This script reads
 [`Python/executor_cases.c.h`](../Python/executor_cases.c.h) (which is
 generated from [`Python/bytecodes.c`](../Python/bytecodes.c)). For
 each opcode, it constructs a `.c` file that contains a function for
 implementing this opcode, with some runtime information injected.
 This is done by replacing `CASE` by the bytecode definition in the
 template file [`Tools/jit/template.c`](../Tools/jit/template.c).

 Each of the `.c`file is compiled by LLVM, to produce an object file
 Each of the `.c`files is compiled by LLVM, to produce an object file
 that contains a function that executes the opcode. These compiled
 functions are used to generate the file
 [`jit_stencils.h`](../jit_stencils.h), which contains the functions
Original file line number	Diff line number	Diff line change
Expand Up		@@ -18,11 +18,11 @@ Code objects are typically produced by the bytecode [compiler](compiler.md),
		although they are often written to disk by one process and read back in by another.
		The disk version of a code object is serialized using the
		[marshal](https://docs.python.org/dev/library/marshal.html) protocol.
		When a[`CodeObject`](code_objects.md) is created, the function
		`_PyCode_Quicken()` from[`Python/specialize.c`](../Python/specialize.c) is
		called to initializethe caches of all adaptive instructions. This is
		required because theon-disk format is a sequence of bytes, and
		some of the caches need to beinitialized with 16-bit values.
		When a `CodeObject` is created, the function `_PyCode_Quicken()` from
		[`Python/specialize.c`](../Python/specialize.c) is called to initialize
		the caches of all adaptive instructions. This is required because the
		on-disk format is a sequence of bytes, and some of the caches need to be
		initialized with 16-bit values.

		Code objects are nominally immutable.
		Some fields (including `co_code_adaptive` and fields for runtime
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -366,7 +366,7 @@ assumptions still apply, and de-optimizing back to the generic version if not.
		## Families of instructions

		A family of instructions consists of an adaptive instruction along with the
		specializedinstruction that it can be replaced by.
		specializedinstructions that it can be replaced by.
		It has the following fundamental properties:

		* It corresponds to a single instruction in the code
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -86,7 +86,7 @@ have changed.
		When the full jit is enabled (python was configured with
		[`--enable-experimental-jit`](https://docs.python.org/dev/using/configure.html#cmdoption-enable-experimental-jit),
		the uop executor's `jit_code` field is populated with a pointer to a compiled
		C function thatimplement the executor logic. This function's signature is
		C function thatimplements the executor logic. This function's signature is
		defined by `jit_func` in [`pycore_jit.h`](Include/internal/pycore_jit.h).
		When the executor is invoked by `ENTER_EXECUTOR`, instead of jumping to
		the uop interpreter at `tier2_dispatch`, the executor runs the function
Expand All		@@ -101,16 +101,16 @@ of the micro ops, which are completed with runtime information while
		the jitted code is constructed for an executor by
		[`_PyJIT_Compile`](../Python/jit.c).

		The stencils are generated under thebuild target `regen-jit` by the scripts
		in [`/Tools/jit`](/Tools/jit). This script reads
		The stencils are generatedat build timeunder theMakefile target `regen-jit`
		by the scriptsin [`/Tools/jit`](/Tools/jit). This script reads
		[`Python/executor_cases.c.h`](../Python/executor_cases.c.h) (which is
		generated from [`Python/bytecodes.c`](../Python/bytecodes.c)). For
		each opcode, it constructs a `.c` file that contains a function for
		implementing this opcode, with some runtime information injected.
		This is done by replacing `CASE` by the bytecode definition in the
		template file [`Tools/jit/template.c`](../Tools/jit/template.c).

		Each of the `.c`file is compiled by LLVM, to produce an object file
		Each of the `.c`files is compiled by LLVM, to produce an object file
		that contains a function that executes the opcode. These compiled
		functions are used to generate the file
		[`jit_stencils.h`](../jit_stencils.h), which contains the functions
Expand Down