v128.const text #65
v128.const text #65
Conversation
proposals/simd/SIMD.md
Outdated
| v128.const i32x4 i32 i32 i32 i32 | ||
| v128.const i64x2 i64 i64 | ||
| v128.const f32x4 f32 f32 f32 f32 | ||
| v128.const f64x2 f64 f64 |
There was a problem hiding this comment.
We need to keep the text format separate from the design and binary format as this concerns only handwritten wasm tests or debug views of modules. Can we move all text format descriptions in its own section.
There was a problem hiding this comment.
@arunetm the text format will need to be the final spec as well, so it's not just a tool convention. The operations section of SIMD.md also already contains the names of every instruction in the style of the text format chapter of the specification, so I'm not sure this is out of place with respect to the other content in this file. I'm happy to move it, though, if you think that makes more sense. Would you want a separate file specifically for the text format analogous to BinarySIMD.md for the binary encoding?
There was a problem hiding this comment.
Yes, we need Text format to be part of the final spec. However, it's better to separate it from the types and operations ensuring that any references remain consistent. Agree that this is not critical until we have the formal spec, but I think its the right thing to do.
I suggest having a separate file analogous to BinarySIMD.md for text format. Also the added benefit of having a single place to refer to for people hand coding wasm modules.
|
|
As discussed in #55.