Dec 6, 2024 · Nov 22, 2024 · Nov 22, 2024 · Nov 23, 2024 · Nov 28, 2024 · Dec 5, 2024
diff --git a/InternalDocs/jit.md b/InternalDocs/jit.md
 `_Py_SetTier2Optimizer()` function (this is used in test via
 `_testinternalcapi.set_optimizer()`.)

 The micro-opoptimizer(abbreviated `uop` to approximate `μop`) is defined in
 The micro-op (abbreviated `uop` to approximate `μop`) optimizer is defined in
 [`Python/optimizer.c`](../Python/optimizer.c) as the type `_PyUOpOptimizer_Type`.
 It translates an instruction trace into a sequence of micro-ops by replacing
 each bytecode by an equivalent sequence of micro-ops (see
 The micro-op sequence is then optimized by
 `_Py_uop_analyze_and_optimize` in
 [`Python/optimizer_analysis.c`](../Python/optimizer_analysis.c)
 anda `_PyUOpExecutor_Type` is created to contain it.
 andan instance of `_PyUOpExecutor_Type` is created to contain it.

 ##Debugging a uop executor in the JIT interpreter
 ##The JIT interpreter

 After a `JUMP_BACKWARD` instruction invokes the uop optimizer to create a uop
 executor, it transfers control to this executor via the `GOTO_TIER_TWO` macro.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -42,7 +42,7 @@ The optimizer that `_PyOptimizer_Optimize()` runs is configurable via the
		`_Py_SetTier2Optimizer()` function (this is used in test via
		`_testinternalcapi.set_optimizer()`.)

		The micro-opoptimizer(abbreviated `uop` to approximate `μop`) is defined in
		The micro-op (abbreviated `uop` to approximate `μop`) optimizer is defined in
		[`Python/optimizer.c`](../Python/optimizer.c) as the type `_PyUOpOptimizer_Type`.
		It translates an instruction trace into a sequence of micro-ops by replacing
		each bytecode by an equivalent sequence of micro-ops (see
Expand All		@@ -52,9 +52,9 @@ which is generated from [`Python/bytecodes.c`](../Python/bytecodes.c)).
		The micro-op sequence is then optimized by
		`_Py_uop_analyze_and_optimize` in
		[`Python/optimizer_analysis.c`](../Python/optimizer_analysis.c)
		anda `_PyUOpExecutor_Type` is created to contain it.
		andan instance of `_PyUOpExecutor_Type` is created to contain it.

		##Debugging a uop executor in the JIT interpreter
		##The JIT interpreter

Copy link Member markshannonDec 6, 2024 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others.Learn more. Can you add a sentence or two saying why we have this strange looking interpreter? Being able to debug and analyze the optimizations prior independent of machine code generation is vey valuable.
		After a `JUMP_BACKWARD` instruction invokes the uop optimizer to create a uop
		executor, it transfers control to this executor via the `GOTO_TIER_TWO` macro.
Expand Down