diff options
| author | Luke Wagner <luke@mozilla.com> | 2016-03-09 00:07:17 -0600 |
|---|---|---|
| committer | Luke Wagner <luke@mozilla.com> | 2016-03-09 00:07:17 -0600 |
| commit | 2e5548b0ea58becff293e8028c2b06a68f1f738a (patch) | |
| tree | e3a642c7ada30151cf4c54aed191b63e08f82f67 /BinaryEncoding.md | |
| parent | d2b487a60dafacfe2a4683c655326e3cdd45d8c0 (diff) | |
| download | nanowasm-design-2e5548b0ea58becff293e8028c2b06a68f1f738a.tar.gz | |
Revert "Opcodes should also be LEB128; we're definitely going to end up with >256 after SIMD"
This reverts commit b3378e3e6621256ca81e4c9a8f9ac858d6e69a5d (accidental push to master)
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 b6fa3be..09e65f5 100644 --- a/BinaryEncoding.md +++ b/BinaryEncoding.md @@ -63,12 +63,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 ### Strings |