Skip to content

Gate component model functions with multiple returns #1670

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

alexcrichton
Copy link
Member

This commit is an implementation of WebAssembly/component-model#368 in this repository. The intention here is along the lines of a few other recent restrictions which is to avoid outright removing support and instead stage the changes a bit. To that end a new feature flag is added and multi-return functions are now gated behind this feature flag. Tests are updated to avoid using it and otherwise the actual removal of supporting code is deferred to a later date.

This commit is an implementation of WebAssembly/component-model#368 in
this repository. The intention here is along the lines of a few other
recent restrictions which is to avoid outright removing support and
instead stage the changes a bit. To that end a new feature flag is added
and multi-return functions are now gated behind this feature flag. Tests
are updated to avoid using it and otherwise the actual removal of
supporting code is deferred to a later date.
@alexcrichton alexcrichton added this pull request to the merge queue Jul 15, 2024
Merged via the queue into bytecodealliance:main with commit fb42670 Jul 15, 2024
27 checks passed
@alexcrichton alexcrichton deleted the gate-multiple-returns branch July 15, 2024 16:25
alexcrichton added a commit to alexcrichton/wasm-tools that referenced this pull request Jul 24, 2024
This fixes a fuzz issue from bytecodealliance#1670 which wasn't fixed at the time and
has been found on oss-fuzz.
github-merge-queue bot pushed a commit that referenced this pull request Jul 25, 2024
This fixes a fuzz issue from #1670 which wasn't fixed at the time and
has been found on oss-fuzz.
jsturtevant added a commit to hyperlight-dev/hyperlight that referenced this pull request Jun 27, 2025
This was a bit more involved due to a big change in the way function return types are handled.  The orginal change was done in WebAssembly/component-model#368 and put initially put behind a feature flag in bytecodealliance/wasm-tools#1670. In 0.226.0 version of wasmparser this feature flag was removed simplify the return results.  This in turn simplifies the handling of the results here as well.

Signed-off-by: James Sturtevant <[email protected]>
jsturtevant added a commit to hyperlight-dev/hyperlight that referenced this pull request Jun 27, 2025
This was a bit more involved due to a big change in the way function return types are handled.  The orginal change was done in WebAssembly/component-model#368 and put initially put behind a feature flag in bytecodealliance/wasm-tools#1670. In 0.226.0 version of wasmparser this feature flag was removed simplify the return results.  This in turn simplifies the handling of the results here as well.

Signed-off-by: James Sturtevant <[email protected]>
jsturtevant added a commit to hyperlight-dev/hyperlight that referenced this pull request Jul 1, 2025
This was a bit more involved due to a big change in the way function return types are handled.  The orginal change was done in WebAssembly/component-model#368 and put initially put behind a feature flag in bytecodealliance/wasm-tools#1670. In 0.226.0 version of wasmparser this feature flag was removed simplify the return results.  This in turn simplifies the handling of the results here as well.

Signed-off-by: James Sturtevant <[email protected]>
jsturtevant added a commit to hyperlight-dev/hyperlight that referenced this pull request Jul 3, 2025
This was a bit more involved due to a big change in the way function return types are handled.  The orginal change was done in WebAssembly/component-model#368 and put initially put behind a feature flag in bytecodealliance/wasm-tools#1670. In 0.226.0 version of wasmparser this feature flag was removed simplify the return results.  This in turn simplifies the handling of the results here as well.

Signed-off-by: James Sturtevant <[email protected]>
jsturtevant added a commit to hyperlight-dev/hyperlight that referenced this pull request Jul 9, 2025
This was a bit more involved due to a big change in the way function return types are handled.  The orginal change was done in WebAssembly/component-model#368 and put initially put behind a feature flag in bytecodealliance/wasm-tools#1670. In 0.226.0 version of wasmparser this feature flag was removed simplify the return results.  This in turn simplifies the handling of the results here as well.

Signed-off-by: James Sturtevant <[email protected]>
jsturtevant added a commit to hyperlight-dev/hyperlight that referenced this pull request Jul 10, 2025
This was a bit more involved due to a big change in the way function return types are handled.  The orginal change was done in WebAssembly/component-model#368 and put initially put behind a feature flag in bytecodealliance/wasm-tools#1670. In 0.226.0 version of wasmparser this feature flag was removed simplify the return results.  This in turn simplifies the handling of the results here as well.

Signed-off-by: James Sturtevant <[email protected]>
jsturtevant added a commit to hyperlight-dev/hyperlight that referenced this pull request Jul 11, 2025
This was a bit more involved due to a big change in the way function return types are handled.  The orginal change was done in WebAssembly/component-model#368 and put initially put behind a feature flag in bytecodealliance/wasm-tools#1670. In 0.226.0 version of wasmparser this feature flag was removed simplify the return results.  This in turn simplifies the handling of the results here as well.

Signed-off-by: James Sturtevant <[email protected]>
jsturtevant added a commit to hyperlight-dev/hyperlight that referenced this pull request Jul 14, 2025
This was a bit more involved due to a big change in the way function return types are handled.  The orginal change was done in WebAssembly/component-model#368 and put initially put behind a feature flag in bytecodealliance/wasm-tools#1670. In 0.226.0 version of wasmparser this feature flag was removed simplify the return results.  This in turn simplifies the handling of the results here as well.

Signed-off-by: James Sturtevant <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants