Changes in .gitmodules

38b408c3 - Run `*.wast` tests from component-model repo (#11677)

Wed, 10 Sep 2025 23:24:28 +0000

Run `*.wast` tests from component-model repo (#11677)* Run `*.wast` tests from component-model repoThis adds a new submodule like WebAssembly/testsuite for thecomponent-model spec tests and runs the `*.wast` tests on all changes.There are two currently failing tests which are relegated to #11675and #11676 for now.* Update submodule to a fixed test* Remove now-duplicate tests* Disable component-model-async with Winch List of files: /wasmtime-44.0.1/.gitmodules

71d576e3 - wasi-nn: remove Git submodule (#8519)

Thu, 02 May 2024 18:28:30 +0000

wasi-nn: remove Git submodule (#8519)* wasi-nn: remove Git submoduleTo more closely align with the conventions in the `wasmtime-wasi` and`wasmtime-wasi-http` crates, this change removes the Git submodule thatpreviously provided the WIT and WITX files for `wasmtime-wasi-nn`. Likethose other crates, the syncing of wasi-nn WIT and WITX files willhappen manually for the time being. This is the first PR towardsupgrading the wasi-nn implementation to match recent spec changes andbetter preview2-ABI compatibility.prtest:full* ci: auto-vendor the wasi-nn WIT files List of files: /wasmtime-44.0.1/.gitmodules

8f03b22e - Remove wasm-c-api submodule (#8170)

Mon, 18 Mar 2024 18:58:11 +0000

Remove wasm-c-api submodule (#8170)* Remove wasm-c-api submoduleThis submodule hasn't been updated in ~3 years at this point and weadditionally don't need most of the submodule. Instead add a script tocopy the files we need and verify in CI that the files are up-to-date.This also makes using the C API a bit nicer where you don't have to havetwo `include` directories with a Wasmtime source tree, just onesuffices.* Don't format wasm.h{,h} vendored files List of files: /wasmtime-44.0.1/.gitmodules

51ed1350 - Remove the `WASI` submodule (#7984)

Thu, 22 Feb 2024 22:23:42 +0000

Remove the `WASI` submodule (#7984)* Remove the `WASI` submoduleHistorically the `WASI` submodule in this repository was used to pullthe sources of the `*.witx` files for preview1. This has never been usedby the `wasmtime-wasi` crate (which has its own copy in the`crates/wasi/witx` folder) and was only ever used by `wasi-common`. Thissubmodule also served as a location for the `witx` crate itself.Neither of these are really needed any more as the `*.witx` files areunlikely to ever really change again. This commit removes the submoduleentirely, as well as the `path` dependency on `witx`, and copies the`*.witx` files in the same manner as the `wasmtime-wasi` crate.* Updated vet entries for witx* Remove witx special cases in publish script* Change how the wasi-common package is built List of files: /wasmtime-44.0.1/.gitmodules

6875e268 - Remove submodule re-added by accident (#7008)

Tue, 12 Sep 2023 20:17:33 +0000

Remove submodule re-added by accident (#7008)This was removed in #6195 but re-added in #6877, I believe by accident,so this re-deletes it. I've also edited `.gitmodules` a bit while I washere to remove it and additionally keep other entries up-to-date withmatching paths. List of files: /wasmtime-44.0.1/.gitmodules

2897e409 - Remove the implementation of wasi-crypto (#6816)

Tue, 08 Aug 2023 15:43:59 +0000

Remove the implementation of wasi-crypto (#6816)* Remove the implementation of wasi-cryptoThis commit is a follow-up to the discussion on #6732. This removesWasmtime's implementation of the wasi-crypto proposal from in-tree alongwith its various support in CI, configuration, etc. See the discussionon #6732 for the full information but at a high level the main reasonsfor removing the implementation at this time are:* There is not currently an active maintainer of the Wasmtime integration here for wasi-crypto.* There are known issues with the code quality of the implementation such as transmutes of guest-owned memory to `&'static mut [u8]` and known unsafety in dependencies.* The size and breadth of the dependency tree brings maintenance burden and overhead to managing Wasmtime's dependency tree.As mentioned on the issue this commit does not mean that Wasmtimedoesn't want to implement the wasi-crypto proposal. Instead the "tier 3"status of wasi-crypto needs to be re-attained to be included backin-tree, which would mean resolving the above issues.Note that this commit is intentionally just after the 13.0.0 branchpoint which means that this is slated for Wasmtime 14 to be released onSeptember 20.* Remove some cfgs* Remove wasi-crypto CI List of files: /wasmtime-44.0.1/.gitmodules

1a6b3ec1 - test: add cases from `wasi-testsuite` (#6341)

Thu, 04 May 2023 20:15:37 +0000

test: add cases from `wasi-testsuite` (#6341)* wasi: add the `wasi-testsuite` tests for wasi-commonAs described [here], this uses the `prod/testsuite-base` branch in whichthe tests are built as `.wasm` files.[here]: https://github.com/WebAssembly/wasi-testsuite/#getting-started* chore: update `walkdir` everywhere to its latest versionThis is done in order to use it for `wasi_testsuite` testing.* vet: extend `walkdir`'s exemption* test: factor out `get_wasmtime_command`This will be helpful for `wasi_testsuite` testing.* test: use all `wasi-testsuite` test casesThis change alters the `wasi_testsuite` test to run all of the availabletest cases in [wasi-testsuite]. This involved making the test runner abit more robust to the various shapes of JSON specifications in thatproject. Unfortunately, the `wasi_testsuite` test fails some of thecases, so I added a `WASI_COMMON_IGNORE_LIST` to avoid thesetemporarily. (This may remind some of the Wasm testsuite ignore lists inCranelift; those relied on `build.rs` to create a `#[test]` for eachtest case, which I felt is not yet needed here).It's unclear to me why the tests are failing. It could be because:- wasi-common has a bug- wasi-testsuite overspecifies (or incorrectly specifies) a test- the test runner incorrectly configures Wasmtime's CLI execution.But this change makes it easier to resolve this. Remove the file from`WASI_COMMON_IGNORE_LIST` and run `cargo test wasi_testsuite ----nocapture`. The printed output will show the expected result, theactual result, and a command to replicate the failure from the commandline.[wasi-testsuite]: https://github.com/WebAssembly/wasi-testsuite* review: add "shrinking" comment List of files: /wasmtime-44.0.1/.gitmodules

2d34dbef - Begin implementation of wasi-http (#5929)

Wed, 05 Apr 2023 20:33:03 +0000

Begin implementation of wasi-http (#5929)* Integrate experimental HTTP into wasmtime.* Reset Cargo.lock* Switch to bail!, plumb options partially.* Implement timeouts.* Remove generated files & wasm, add Makefile* Remove generated code textfile* Update crates/wasi-http/Cargo.tomlCo-authored-by: Eduardo de Moura Rodrigues <16357187+eduardomourar@users.noreply.github.com>* Update crates/wasi-http/Cargo.tomlCo-authored-by: Eduardo de Moura Rodrigues <16357187+eduardomourar@users.noreply.github.com>* Extract streams from request/response.* Fix read for len < buffer length.* Formatting.* types impl: swap todos for traps* streams_impl: idioms, and swap todos for traps* component impl: idioms, swap all unwraps for traps, swap all todos for traps* http impl: idiom* Remove an unnecessary mut.* Remove an unsupported function.* Switch to the tokio runtime for the HTTP request.* Add a rust example.* Update to latest wit definition* Remove example code.* wip: start writing a http test...* finish writing the outbound request examplehavent executed it yet* better debug output* wasi-http: some stubs required for rust rewrite of the example* add wasi_http tests to test-programs* CI: run the http tests* Fix some warnings.* bump new deps to latest releases (#3)* Add tests for wasi-http to test-programs (#2) * wip: start writing a http test... * finish writing the outbound request example havent executed it yet * better debug output * wasi-http: some stubs required for rust rewrite of the example * add wasi_http tests to test-programs * CI: run the http tests * bump new deps to latest releases h2 0.3.16 http 0.2.9 mio 0.8.6 openssl 0.10.48 openssl-sys 0.9.83 tokio 1.26.0 --------- Co-authored-by: Brendan Burns * Update crates/test-programs/tests/http_tests/runtime/wasi_http_tests.rs* Update crates/test-programs/tests/http_tests/runtime/wasi_http_tests.rs* Update crates/test-programs/tests/http_tests/runtime/wasi_http_tests.rs* wasi-http: fix cargo.toml file and publish script to work together (#4)unfortunately, the publish script doesn't use a proper toml parser (in order to not have any dependencies), so the whitespace has to be the trivial expected case. then, add wasi-http to the list of crates to publish.* Update crates/test-programs/build.rs* Switch to rustls* Cleanups.* Merge switch to rustls.* Formatting* Remove libssl install* Fix tests.* Rename wasi-http -> wasmtime-wasi-http* prtest:fullConditionalize TLS on riscv64gc.* prtest:fullFix formatting, also disable tls on s390x* prtest:fullAdd a path parameter to wit-bindgen, remove symlink.* prtest:fullFix tests for places where SSL isn't supported.* Update crates/wasi-http/Cargo.toml---------Co-authored-by: Eduardo de Moura Rodrigues <16357187+eduardomourar@users.noreply.github.com>Co-authored-by: Pat Hickey Co-authored-by: Pat Hickey List of files: /wasmtime-44.0.1/.gitmodules

ad584f42 - wasi-threads: run test suite (#5907)

Sat, 04 Mar 2023 21:50:15 +0000

wasi-threads: run test suite (#5907)* wasi-threads: run test suiteThis change enables the running of the wasi-threads [test suite]. Itrelies on a Wasmtime CLI binary being available and runs all `*.wasm`and `*.wat` files present in the test suite directory. The results ofeach execution are compared against a JSON spec file with the same basename as the WebAssembly module. The spec file defines the expected exitcode, e.g.This commit does not yet build any `*.c` or `*.s` files from the testsuite. That could be done later, perhaps upstream; in the meantime, thiswork is still valuable as it lays the foundation for running other WASItests from the in-progress [wasi-testsuite] which share the same JSONspec infrastructure.[test suite]: https://github.com/WebAssembly/wasi-threads/tree/main/test/testsuite[wasi-testsuite]: https://github.com/WebAssembly/wasi-testsuite* review: move testsuite to top-level tests* fix: remove now-unnecessary wasi-threads test* fix: update testsuite submodule name* fix: ignore tests on Windowsprtest:full* fix: `cfg_attr` syntaxprtest:full List of files: /wasmtime-44.0.1/.gitmodules

42acb72c - fuzz: retrieve the WebAssembly spec repository in `build.rs`

Tue, 10 Aug 2021 18:08:30 +0000

fuzz: retrieve the WebAssembly spec repository in `build.rs`To avoid the large download size of the spec repository mentioned[here](https://github.com/bytecodealliance/wasmtime/pull/3124#discussion_r684605984),this change removes it as a submodule and instead clones it shallowlywhen the directory is empty (or not present) when `build.rs` is run. List of files: /wasmtime-44.0.1/.gitmodules

a7f592a0 - Add a crate to interface with the WebAssembly spec interpreter

Wed, 28 Jul 2021 20:12:47 +0000

Add a crate to interface with the WebAssembly spec interpreterThe WebAssembly spec interpreter is written in OCaml and the new crateuses `ocaml-interop` along with a small OCaml wrapper to interpret Wasmmodules in-process. The build process for this crate is currentlyLinux-specific: it requires several OCaml packages (e.g. `apt install -yocaml-nox ocamlbuild`) as well as `make`, `cp`, and `ar`. List of files: /wasmtime-44.0.1/.gitmodules

cc6bde52 - Update wasi-nn submodule

Thu, 18 Feb 2021 18:01:48 +0000

Update wasi-nn submodule List of files: /wasmtime-44.0.1/.gitmodules

d095f63c - Update submodules

Thu, 18 Feb 2021 17:50:35 +0000

Update submodules List of files: /wasmtime-44.0.1/.gitmodules

9ab5fa26 - Update the wasi-crypto spec

Wed, 17 Feb 2021 22:29:38 +0000

Update the wasi-crypto spec List of files: /wasmtime-44.0.1/.gitmodules

250f11c5 - Fix build of wasi-nn

Wed, 17 Feb 2021 22:16:18 +0000

Fix build of wasi-nn List of files: /wasmtime-44.0.1/.gitmodules

df9c725f - Update to the next version of the witx crate

Thu, 11 Feb 2021 17:28:36 +0000

Update to the next version of the witx crateThis commit updates to the 0.9 version of the witx crate implemented inWebAssembly/wasi#395. This new version drastically changes codegeneration and how we interface with the crate. The intention is toabstract the code generation aspects and allow code generators toimplement much more low-level instructions to enable more flexible APIsin the future. Additionally a bunch of `*.witx` files were updated inthe WASI repository.It's worth pointing out, however, that `wasi-common` does not change asa result of this change. The shape of the APIs that we need to implementare effectively the same and the only difference is that the shimfunctions generated by wiggle are a bit different. List of files: /wasmtime-44.0.1/.gitmodules

a0fad606 - Add support for the experimental wasi-crypto APIs (#2597)

Mon, 25 Jan 2021 15:32:58 +0000

Add support for the experimental wasi-crypto APIs (#2597)* Add support for the experimental wasi-crypto APIs The sole purpose of the implementation is to allow bindings and application developers to test the proposed APIs. Rust and AssemblyScript bindings are also available as examples. Like `wasi-nn`, it is currently disabled by default, and requires the `wasi-crypto` feature flag to be compiled in. * Rename the wasi-crypto/spec submodule * Add a path dependency into the submodule for wasi-crypto * Tell the publish script to vendor wasi-crypto List of files: /wasmtime-44.0.1/.gitmodules

a61f068c - Add an initial wasi-nn implementation for Wasmtime (#2208)

Mon, 16 Nov 2020 18:54:00 +0000

Add an initial wasi-nn implementation for Wasmtime (#2208)* Add an initial wasi-nn implementation for Wasmtime This change adds a crate, `wasmtime-wasi-nn`, that uses `wiggle` to expose the current state of the wasi-nn API and `openvino` to implement the exposed functions. It includes an end-to-end test demonstrating how to do classification using wasi-nn: - `crates/wasi-nn/tests/classification-example` contains Rust code that is compiled to the `wasm32-wasi` target and run with a Wasmtime embedding that exposes the wasi-nn calls - the example uses Rust bindings for wasi-nn contained in `crates/wasi-nn/tests/wasi-nn-rust-bindings`; this crate contains code generated by `witx-bindgen` and eventually should be its own standalone crate * Test wasi-nn as a CI step This change adds: - a GitHub action for installing OpenVINO - a script, `ci/run-wasi-nn-example.sh`, to run the classification example List of files: /wasmtime-44.0.1/.gitmodules

968cd761 - Move back to only one WASI submodule (#1434)

Mon, 30 Mar 2020 19:45:23 +0000

Move back to only one WASI submodule (#1434)* Move back to only one WASI submodule This commit fixes the issue where we have two WASI submodules for build reasons in this repository. The fix was to place the submodule in the `wasi-common` crate, and then anyone using the `wig` crate has to be sure to define a `WASI_ROOT` env var in a build script to be able to parse witx files. With all that in place `wasi-common` becomes the source of truth for the witx files we're parsing, and crates like `wasmtime-wasi` use build-scripts shenanigans to read the same witx files. This should hopefully get us so we're compatible with publishing and still only have one submodule! * rustfmt List of files: /wasmtime-44.0.1/.gitmodules

6c0c9a46 - Fixes for cargo publish (#1416)

Fri, 27 Mar 2020 03:31:12 +0000

Fixes for cargo publish (#1416)* Publishing fixes. * Make WASI a symlink. * More fixes. * Cargo doesn't allow dev-dependencies to have optional features. * Remove the symlink. * Add WASI as another git submodule. List of files: /wasmtime-44.0.1/.gitmodules