Add a new -Sp3 option to the CLI
#11423
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit adds a new WASI-specific CLI option dubbed "p3" which controls whether WASIp3 interfaces are added to the component linker and whether WASIp3 exports are searched for. Integration here is only added with `wasmtime run` and support for `wasmtime serve` will come once wasi:http is migrated to this repository from the p3-prototyping repository. The `-Sp3` option is off-by-default at this time but this is structured to enable it by default in the future. A test is added to ensure that WASIp3 is usable and a basic "hello world" works. Some internal refactoring was done to share more code between `run` and `serve` with respect to adding WASI interfaces to a linker.
dicej
approved these changes
Aug 12, 2025
bongjunj
pushed a commit
to prosyslab/wasmtime
that referenced
this pull request
Oct 20, 2025
* Add a new `-Sp3` option to the CLI This commit adds a new WASI-specific CLI option dubbed "p3" which controls whether WASIp3 interfaces are added to the component linker and whether WASIp3 exports are searched for. Integration here is only added with `wasmtime run` and support for `wasmtime serve` will come once wasi:http is migrated to this repository from the p3-prototyping repository. The `-Sp3` option is off-by-default at this time but this is structured to enable it by default in the future. A test is added to ensure that WASIp3 is usable and a basic "hello world" works. Some internal refactoring was done to share more code between `run` and `serve` with respect to adding WASI interfaces to a linker. * Use a normal blocking test * Fix warning
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit adds a new WASI-specific CLI option dubbed "p3" which controls whether WASIp3 interfaces are added to the component linker and whether WASIp3 exports are searched for. Integration here is only added with
wasmtime runand support forwasmtime servewill come once wasi:http is migrated to this repository from the p3-prototyping repository.The
-Sp3option is off-by-default at this time but this is structured to enable it by default in the future. A test is added to ensure that WASIp3 is usable and a basic "hello world" works.Some internal refactoring was done to share more code between
runandservewith respect to adding WASI interfaces to a linker.Closes bytecodealliance/wasip3-prototyping#108