diff options
| author | Luke Wagner <luke@mozilla.com> | 2016-03-09 10:50:52 -0600 |
|---|---|---|
| committer | Luke Wagner <luke@mozilla.com> | 2016-03-09 10:52:29 -0600 |
| commit | a3ace6fb6e54ea2a7612d77745c590e4a90c09b7 (patch) | |
| tree | a9342c7e45549fe64f9d082c086b4727276b32e5 /BinaryEncoding.md | |
| parent | 369abe553e96dc2ebbe847f4c6a76f05e5c6ef2d (diff) | |
| download | nanowasm-design-a3ace6fb6e54ea2a7612d77745c590e4a90c09b7.tar.gz | |
Revert "Opcodes should also be LEB128; we're definitely going to end up with >256 after SIMD"
This reverts commit edac92d9e10e5fb3ea8e305236c6d00da05a8d48
Diffstat (limited to 'BinaryEncoding.md')
| -rw-r--r-- | BinaryEncoding.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/BinaryEncoding.md b/BinaryEncoding.md index ca988b7..ad77763 100644 --- a/BinaryEncoding.md +++ b/BinaryEncoding.md @@ -57,12 +57,12 @@ sequence, then followed recursively by any child nodes. * Examples * Given a simple AST node: `I32Add(left: AstNode, right: AstNode)` - * First write the opcode for `I32Add` (`varuint32`) + * First write the opcode for `I32Add` (uint8) * Then recursively write the left and right nodes. * Given a call AST node: `Call(callee_index: uint32_t, args: AstNode[])` - * First write the opcode of `Call` (`varuint32`) - * Then write the (variable-length) integer `callee_index` (`varuint32`) + * First write the opcode of `Call` (uint8) + * Then write the (variable-length) integer `callee_index` (varuint32) * Then recursively write each argument node, where arity is determined by looking up `callee_index` in a table of signatures # Module structure |