From 2e5548b0ea58becff293e8028c2b06a68f1f738a Mon Sep 17 00:00:00 2001 From: Luke Wagner Date: Wed, 9 Mar 2016 00:07:17 -0600 Subject: 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) --- BinaryEncoding.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'BinaryEncoding.md') 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 -- cgit v1.2.3