Skip to content
This repository was archived by the owner on Dec 22, 2021. It is now read-only.
This repository was archived by the owner on Dec 22, 2021. It is now read-only.

Tracking instructions with unassigned opcodes #421

Closed

Description

@tlively

We don't want to do another full renumbering, but we also want to choose reasonable opcodes for new instructions, so we decided here and in the 1/8/21 meeting that beginning with #376, the final opcodes of all newly merged instructions will be decided after we finalize the instruction set. The opcodes of instructions merged earlier than #376 will not change.

Here is a (hopefully up-to-date) list of instructions whose opcodes will need to be finalized:

Activity

  1. Maratyszcza commented on Jan 8, 2021

    @Maratyszcza
    Contributor

    A couple more:

    • v128.any_true instruction to replace i8x16.any_true/i16x8.any_true/i32x4.any_true/i64x2.any_true (any_true instructions should be untyped #416)
    • Potentially floating-point rounding instructions, as their opcodes overlap with 64-bit min/max reserved opcodes
  2. ngzhian commented on Mar 10, 2021

    @ngzhian
    Member

    Closing, this is done, and superseded by #452

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions