We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On https://webassembly.github.io/spec/core/appendix/index-instructions.html the opcodes for vector instructions are all two bytes, from 0xFD 0x00 -> 0xFD 0xFF, for example f64x2.convert_low_i32x4_u is listed as 0xFD 0xFF:
f64x2.convert_low_i32x4_u
spec/document/core/appendix/index-instructions.rst
Line 517 in d391957
On https://webassembly.github.io/spec/core/binary/instructions.html#vector-instructions it states
They all have a one byte prefix, whereas the actual opcode is encoded by a variable-length unsigned integer
and f64x2.convert_low_i32x4_u is listed as 0xFD 255:u32, which I believe is effectively 0xFD 0xFF 0x01.
spec/document/core/binary/instructions.rst
Line 836 in d391957
The text was updated successfully, but these errors were encountered:
Indeed!
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
On https://webassembly.github.io/spec/core/appendix/index-instructions.html the opcodes for vector instructions are all two bytes, from 0xFD 0x00 -> 0xFD 0xFF, for example
f64x2.convert_low_i32x4_u
is listed as 0xFD 0xFF:spec/document/core/appendix/index-instructions.rst
Line 517 in d391957
On https://webassembly.github.io/spec/core/binary/instructions.html#vector-instructions it states
and
f64x2.convert_low_i32x4_u
is listed as 0xFD 255:u32, which I believe is effectively 0xFD 0xFF 0x01.spec/document/core/binary/instructions.rst
Line 836 in d391957
The text was updated successfully, but these errors were encountered: