summaryrefslogtreecommitdiff
path: root/test/lit/arrays.wast
diff options
context:
space:
mode:
authorThomas Lively <tlively@google.com>2024-01-03 12:55:00 -0800
committerGitHub <noreply@github.com>2024-01-03 12:55:00 -0800
commita6bc9542e98b4164d3a26c67c94b1136b4fc8b86 (patch)
tree50c3408c4a9a0d9a6cef73780364caff8826fe90 /test/lit/arrays.wast
parent260fdfcdaaeba3f4a47ef057db28c61203c8d3b1 (diff)
downloadbinaryen-a6bc9542e98b4164d3a26c67c94b1136b4fc8b86.tar.gz
binaryen-a6bc9542e98b4164d3a26c67c94b1136b4fc8b86.tar.bz2
binaryen-a6bc9542e98b4164d3a26c67c94b1136b4fc8b86.zip
[Parser] Parse folded instructions that contain parentheses (#6196)
To parse folded instructions in the right order, we need to defer parsing each instruction until we have parsed each of its children and found its closing parenthesis. Previously we naively looked for parentheses to determine where instructions began and ended before we parsed them, but that scheme did not correctly handle instructions that can contain parentheses in their immediates, such as call_indirect. Fix the problem by using the actual instruction parser functions with a placeholder context to find the end of the instructions, including any kind of immediates they might have.
Diffstat (limited to 'test/lit/arrays.wast')
0 files changed, 0 insertions, 0 deletions