Tracking instructions with unassigned opcodes
tlively opened this issue · 2 comments
tlively commented
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:
Maratyszcza commented
A couple more:
v128.any_true
instruction to replacei8x16.any_true
/i16x8.any_true
/i32x4.any_true
/i64x2.any_true
(#416)- Potentially floating-point rounding instructions, as their opcodes overlap with 64-bit
min
/max
reserved opcodes