The bytecode now contains inline cache entries,

which take the form of the newly-added :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.

.. _whatsnew311-added-opcodes:

New opcodes

* :opcode:`ASYNC_GEN_WRAP`, :opcode:`RETURN_GENERATOR` and :opcode:`SEND`,

used in generators and co-routines.

* :opcode:`COPY_FREE_VARS`,

which avoids needing special caller-side code for closures.

* :opcode:`JUMP_BACKWARD_NO_INTERRUPT`,

for use in certain loops where handling interrupts is undesirable.

* :opcode:`MAKE_CELL`, to create :ref:`cell-objects`.

* :opcode:`CHECK_EG_MATCH` and :opcode:`PREP_RERAISE_STAR`,

to handle the :ref:`new exception groups and except* <whatsnew311-pep654>`

added in :pep:`654`.

* :opcode:`PUSH_EXC_INFO`, for use in exception handlers.

* :opcode:`RESUME`, a no-op,

for internal tracing, debugging and optimization checks.

.. _whatsnew311-replaced-opcodes:

| Replaced Opcode(s) | New Opcode(s) | Notes |

| | :opcode:`!BINARY_*` | :opcode:`BINARY_OP` | Replaced all numeric binary/in-place |

| | :opcode:`!INPLACE_*` | | opcodes with a single opcode |

| | :opcode:`!CALL_FUNCTION` | | :opcode:`CALL` | Decouples argument shifting for methods |

| | :opcode:`!CALL_FUNCTION_KW` | | :opcode:`KW_NAMES` | from handling of keyword arguments; |

| | :opcode:`!CALL_METHOD` | | :opcode:`PRECALL` | allows better specialization of calls |

| | | :opcode:`PUSH_NULL` | |

| | :opcode:`!DUP_TOP` | | :opcode:`COPY` | Stack manipulation instructions |

| | :opcode:`!DUP_TOP_TWO` | | :opcode:`SWAP` | |

| | :opcode:`!ROT_TWO` | | |

| | :opcode:`!ROT_THREE` | | |

| | :opcode:`!ROT_FOUR` | | |

| | :opcode:`!ROT_N` | | |

| | :opcode:`!JUMP_IF_NOT_EXC_MATCH` | | :opcode:`CHECK_EXC_MATCH` | Now performs check but doesn't jump |

| | :opcode:`!JUMP_ABSOLUTE` | | :opcode:`JUMP_BACKWARD` | See [#bytecode-jump]_; |

| | :opcode:`!POP_JUMP_IF_FALSE` | | :opcode:`POP_JUMP_BACKWARD_IF_* | ``TRUE``, ``FALSE``, |

| | :opcode:`!POP_JUMP_IF_TRUE` | <POP_JUMP_BACKWARD_IF_TRUE>` | ``NONE`` and ``NOT_NONE`` variants |

| | | :opcode:`POP_JUMP_FORWARD_IF_* | for each direction |

| | <POP_JUMP_FORWARD_IF_TRUE>` | |

| | :opcode:`!SETUP_WITH` | :opcode:`BEFORE_WITH` | :keyword:`with` block setup |

| | :opcode:`!SETUP_ASYNC_WITH` | | |

.. [#bytecode-jump] All jump opcodes are now relative, including the

.. _whatsnew311-changed-opcodes:

.. _whatsnew311-removed-opcodes:

.. _whatsnew311-changed-removed-opcodes:

Changed/removed opcodes

* Changed :opcode:`MATCH_CLASS` and :opcode:`MATCH_KEYS`

to no longer push an additional boolean value to indicate success/failure.

Instead, ``None`` is pushed on failure

in place of the tuple of extracted values.

* Changed opcodes that work with exceptions to reflect them

now being represented as one item on the stack instead of three

(see :gh:`89874`).

* Removed :opcode:`!COPY_DICT_WITHOUT_KEYS`, :opcode:`!GEN_START`,

:opcode:`!POP_BLOCK`, :opcode:`!SETUP_FINALLY` and :opcode:`!YIELD_FROM`.