diff options
| author | Thomas Lively <tlively@google.com> | 2023-12-12 17:20:32 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2023-12-12 17:20:32 -0800 |
| commit | 28bea549061d88a8a7f7d05f3acf3bca175f0102 (patch) | |
| tree | 2329f4374061006771672c7d37001783eaaf06a5 /src/passes/TupleOptimization.cpp | |
| parent | b59b2fc639a134260458bc076c407e7fbfb946d6 (diff) | |
| download | binaryen-28bea549061d88a8a7f7d05f3acf3bca175f0102.tar.gz binaryen-28bea549061d88a8a7f7d05f3acf3bca175f0102.tar.bz2 binaryen-28bea549061d88a8a7f7d05f3acf3bca175f0102.zip | |
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.
Diffstat (limited to 'src/passes/TupleOptimization.cpp')
| -rw-r--r-- | src/passes/TupleOptimization.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/passes/TupleOptimization.cpp b/src/passes/TupleOptimization.cpp index 16a2bad58..25da1c5ec 100644 --- a/src/passes/TupleOptimization.cpp +++ b/src/passes/TupleOptimization.cpp @@ -22,7 +22,7 @@ // (local.set $tuple // (tuple.make 3 (A) (B) (C))) // (use -// (tuple.extract 0 +// (tuple.extract 3 0 // (local.get $tuple))) // // If there are no other uses, then we just need one of the three lanes. By |