.. versionadded:: 3.11
+.. opcode:: CACHE
+
+ Rather than being an actual instruction, this opcode is used to mark extra
+ space for the interpreter to cache useful data directly in the bytecode
+ itself. It is automatically hidden by all ``dis`` utilities, but can be
+ viewed with ``show_caches=True``.
+
+ Logically, this space is part of the preceding instruction. Many opcodes
+ expect to be followed by an exact number of caches, and will instruct the
+ interpreter to skip over them at runtime.
+
+ Populated caches can look like arbitrary instructions, so great care should
+ be taken when reading or modifying raw, adaptive bytecode containing
+ quickened data.
+
+ .. versionadded:: 3.11
+
+
**Unary operations**
Unary operations take the top of the stack, apply the operation, and push the
CPython bytecode changes
========================
+* The bytecode now contains inline cache entries, which take the form of
+ :opcode:`CACHE` instructions. Many opcodes expect to be followed by an exact
+ number of caches, and instruct the interpreter to skip over them at runtime.
+ Populated caches can look like arbitrary instructions, so great care should be
+ taken when reading or modifying raw, adaptive bytecode containing quickened
+ data.
+
* Replaced all numeric ``BINARY_*`` and ``INPLACE_*`` instructions with a single
:opcode:`BINARY_OP` implementation.