From 28bea549061d88a8a7f7d05f3acf3bca175f0102 Mon Sep 17 00:00:00 2001 From: Thomas Lively Date: Tue, 12 Dec 2023 17:20:32 -0800 Subject: Add an arity immediate to tuple.extract (#6172) Once support for tuple.extract lands in the new WAT parser, this arity immediate will let the parser determine how many values it should pop off the stack to serve as the tuple operand to `tuple.extract`. This will usually coincide with the arity of a tuple-producing instruction on top of the stack, but in the spirit of treating the input as a proper stack machine, it will not have to and the parser will still work correctly. --- test/exception-handling.wast.fromBinary.noDebugInfo | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'test/exception-handling.wast.fromBinary.noDebugInfo') diff --git a/test/exception-handling.wast.fromBinary.noDebugInfo b/test/exception-handling.wast.fromBinary.noDebugInfo index beea8498b..b0da0391b 100644 --- a/test/exception-handling.wast.fromBinary.noDebugInfo +++ b/test/exception-handling.wast.fromBinary.noDebugInfo @@ -47,12 +47,12 @@ (local.set $0 (block (result i32) (local.set $3 - (tuple.extract 0 + (tuple.extract 2 0 (local.get $2) ) ) (local.set $1 - (tuple.extract 1 + (tuple.extract 2 1 (local.get $2) ) ) -- cgit v1.2.3