Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
gh-9256: allocate opcode IDs for internal opcodes in their own range
  • Loading branch information
iritkatriel committed Sep 11, 2023
commit b5e1a0594f3c8245d66dfa45b666bef114f9eca2
4 changes: 2 additions & 2 deletions Doc/library/dis.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1611,8 +1611,8 @@ iterations of the loop.
opcodes in the range [0,255] which don't use their argument and those
that do (``< HAVE_ARGUMENT`` and ``>= HAVE_ARGUMENT``, respectively).

If your application uses pseudo instructions, use the :data:`hasarg`
collection instead.
If your application uses pseudo instructions or specialized instructions,
use the :data:`hasarg` collection instead.

.. versionchanged:: 3.6
Now every instruction has an argument, but opcodes ``< HAVE_ARGUMENT``
Expand Down
194 changes: 97 additions & 97 deletions Include/internal/pycore_opcode_metadata.h

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading