Skip to content
This repository was archived by the owner on Aug 2, 2022. It is now read-only.

Support proper spec compliant call_indirect wast syntax#1366

Merged
wanderingbort merged 1 commit intomasterfrom
support_proper_call_indirect_wat_syntax
Feb 12, 2018
Merged

Support proper spec compliant call_indirect wast syntax#1366
wanderingbort merged 1 commit intomasterfrom
support_proper_call_indirect_wat_syntax

Conversation

@spoonincode
Copy link
Copy Markdown
Contributor

The wasm spec has a different definition for the call_indirect syntax in textual representation then what we currently support. Add code to support the spec’s syntax as newer binaryen (s2wasm) seems to use the spec’s syntax.

Be aware, this might still not be TECHNICALLY to spec — I think the spec may allow for defining the function prototype right at the call_indirect site. We only support usage of a type name or type index at the call_indirect site.

Fixes issue #1355

The wasm spec has a different definition for the call_indirect syntax in textual representation then what we currently support. Add code to support the spec’s syntax as newer binaryen (s2wasm) seems to use the spec’s syntax.

Be aware, this might still not be TECHNICALLY to spec — I think the spec may allow for defining the function prototype right at the call_indirect site. We only support usage of a type name or type index at the call_indirect site.
@wanderingbort wanderingbort merged commit 5cdd69c into master Feb 12, 2018
@heifner heifner deleted the support_proper_call_indirect_wat_syntax branch February 13, 2018 12:58
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants