Changes in wasmtime.rs

94740588 - Migrate the Wasmtime CLI to `wasmtime::error` (#12295)

Fri, 09 Jan 2026 19:15:48 +0000

Migrate the Wasmtime CLI to `wasmtime::error` (#12295)* Migrate wasmtime-cli to `wasmtime::error`* migrate benches to `wasmtime::error` as well* Remove new usage of anyhow that snuck in List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

4898322a - Update MSRV to 1.90.0 (#12167)

Thu, 18 Dec 2025 18:44:32 +0000

Update MSRV to 1.90.0 (#12167)* Update MSRV to 1.90.0Coupled with last week's release of 1.92.0.prtest:full* Fix some warnings* Fix another warning List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

18aff9aa - Integrate wizer into this repository (#11805)

Mon, 13 Oct 2025 19:33:52 +0000

Integrate wizer into this repository (#11805)* Remove misc wizer-related files* Integrate the Wizer manifest with this repo's workspace* Enable some more wasmtime features* Get wizer tests passing in-repo* Remove duplicate dummy wizer module* Integer `wasmtime wizer` subcommand into the CLI* Fully integrate wizer into `wasmtime` CLI* Split `wasmtime run` into helper functions* Split `Wizer::run` into helper functions* Weave the two together in `wasmtime wizer`The end goal is to have all CLI options in `wasmtime run` applicable for`wasmtime wizer` as well with some light edits between the two. Overallthough we shouldn't have to proactively support commands in one or theother and everything ideally should "just work".* Fix clippy warnings and bench compiles* Fix benchmarks* Create a store-per-iteration* Use the right wasms in the regex benchmark* Get wizer fuzzer building again* Get CLI working again* Run rustfmt* Remove precompiled wasms from the tree35M for some wasms is a bit heavy so instead build them from source.* Update vet configuration for fuzzers/tests* Update publish script with wasmtime-wizer* Fix clippy lint* Some docs and more clippy lintsprtest:full* Relax version requirement* Try to fix asan build* Remove rustflags too* Un-exclude wizer* Adjust publish script* Update lock file after rebase* Integrate bytecodealliance/wizer#139Use deterministic results for relaxed simd operations by default.* Handle preloads in wizer* Appease clippy* Use deterministic relaxed simd in wizer tests List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

3e406d2e - Add a `wasmtime objdump` subcommand (#10405)

Thu, 20 Mar 2025 19:23:59 +0000

Add a `wasmtime objdump` subcommand (#10405)This commit adds an `objdump` subcommand to the `wasmtime` CLI. Like allother subcommands this can be disabled for a more minimal build of theCLI as well. The purpose of this subcommand is to provide aWasmtime-specific spin on the venerable native `objdump` itself. Notablythis brings Wasmtime-specific knowledge for filtering functions, showingWasmtime metadata, etc.This command is intended to look like `objdump` roughly but also hasconfigurable output with various flags and things that can be printed.For now the main Wasmtime additions are showing the address mapsection, stack map section, and trap section of a `*.cwasm` file.This new subcommand replaces the infrastructure of the `disas` testsuite, and now that test suite uses `wasmtime objdump` to generate testexpectations. Additionally the subcommand replaces the Pulley `objdump`example as a more full-featured objdump that also works natively withPulley.The hope is that if we add more binary metadata in the future (such asunwinding tables) that can be relatively easily added here forexploration as well. Otherwise this is mostly just a developerconvenience for Wasmtime developers as well and hopefully doesn't costtoo much in maintenance burden.Closes #10336 List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

719d6739 - Add a `wasmtime completion` subcommand (#9312)

Thu, 26 Sep 2024 04:11:58 +0000

Add a `wasmtime completion` subcommand (#9312)* Add a `wasmtime completion` subcommandThis commit adds a new subcommand to the `wasmtime` CLI which can beused to generate shell completions for the `wasmtime` version that isinstalled. This is relatively easy to do with the `clap_complete` cratewhich is also used with various other clap-based CLIs in Rust togenerate completions.* Fix build List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

d0fbbba4 - Change the CLI's name to `wasmtime` (#9153)

Tue, 20 Aug 2024 17:50:48 +0000

Change the CLI's name to `wasmtime` (#9153)Currently `wasmtime --version` prints `wasmtime-cli ...` which is thepackage name but this changes it to just `wasmtime` to match theexecutable. List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

ffd6bb55 - Remove support for Wasmtime 13-and-prior CLI (#8597)

Thu, 23 May 2024 20:06:20 +0000

Remove support for Wasmtime 13-and-prior CLI (#8597)This commit removes the support in the `wasmtime` CLI for old CLIoptions which were present in Wasmtime 13 and prior. This compatibilitywas added in #7385 and backported to the Wasmtime 14 release #7395.Wasmtime 14.0.0, which did not have this compatibility shim, wasreleased on 2023-10-20. Wasmtime 14.0.3, which restored compatibilitywith this shim, was released on 2023-10-30. This means that Wasmtimesince 2023-10-30 has been warning users about differences in the old andnew CLI.This commit will be released with Wasmtime 22 which will means thatusers will have had an 8-month transition window for warnings tomigrate. The hope is that this is sufficient but it's also not too tooburdensome to carry for longer if necessary. List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

0e9121da - Fix some typos (#8641)

Thu, 16 May 2024 23:21:22 +0000

Fix some typos (#8641)* occurred* winch typos* tests typos* cli typos* fuzz typos* examples typos* docs typos* crates/wasmtime typos* crates/environ typos* crates/cranelift typos* crates/test-programs typos* crates/c-api typos* crates/cache typos* crates other typos* cranelift/codegen/src/isa typos* cranelift/codegen/src other typos* cranelift/codegen other typos* cranelift other typos* ci js typo* .github workflows typo* RELEASES typo* Fix clang-format documentation line---------Co-authored-by: Andrew Brown List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

71951c9c - Enable compiling the Wasmtime CLI to Wasm (#7980)

Fri, 23 Feb 2024 00:13:33 +0000

Enable compiling the Wasmtime CLI to Wasm (#7980)* Enable compiling the Wasmtime CLI to WasmWhile not the most useful thing to do in the world it's kind of neat toplay around with. This builds on the previous work to exclude theruntime from the `wasmtime` crate so it's now possible to compile theWasmtime CLI's `compile` command, and only the `compile` command, towasm itself. This means you can run Wasmtime in Wasmtime!* Fix warning on wasm* Fix some feature combos List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

f9f8a4df - Replace clap attributes with command and arg (#7658)

Fri, 08 Dec 2023 16:19:10 +0000

Replace clap attributes with command and arg (#7658) List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

f050dd43 - Add extended version information to `wasmtime --version` (#7610)

Wed, 29 Nov 2023 22:23:38 +0000

Add extended version information to `wasmtime --version` (#7610)This commit adds some more information to `wasmtime --version` whichincludes the git commit plus the git commit's date. This matches `rustc-V` for example which was additionally copied to `wasm-tools` andmirrored as `wasm-tools -V`.Personally I've found this useful since it can help point to exactcommits and additionally quickly get a sense of how old a version isbased on its commit date presented. List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

a00ff06c - Update some CLI usage help texts (#7408)

Mon, 30 Oct 2023 19:22:12 +0000

Update some CLI usage help texts (#7408)Updating a few locations that I missed from the previous updates. List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

519808fc - Add compatibility shims for Wasmtime 13 CLI (#7385)

Sat, 28 Oct 2023 00:11:19 +0000

Add compatibility shims for Wasmtime 13 CLI (#7385)* Add compatibility shims for Wasmtime 13 CLIThis commit introduces a compatibility shim for the Wasmtime 13 CLI andprior. The goal of this commit is to address concerns raised in #7336and other locations as well. While the new CLI cannot be un-shipped atthis point this PR attempts to ameliorate the situation somewhat througha few avenues:* A complete copy of the old CLI parser is now included in `wasmtime` by default.* The `WASMTIME_NEW_CLI=0` environment variable can force usage of the old CLI parser for the `run` and `compile` commands.* The `WASMTIME_NEW_CLI=1` environment variable can force usage of the new CLI parser.* Otherwise both the old and the new CLI parser are executed. Depending on the result one is selected to be executed, possibly with a warning printed.* If both CLI parsers succeed but produce the same result, then no warning is emitted and execution continues as usual.* If both CLI parsers succeed but produce different results then a warning is emitted indicating this. The warning points to #7384 which has further examples of how to squash the warning. The warning also mentions the above env var to turn the warning off. In this situation the old semantics are used at this time instead of the new semantics. It's intended that eventually this will change in the future.* If the new CLI succeeds and the old CLI fails then the new semantics are executed without warning.* If the old CLI succeeds and the new CLI fails then a warning is issued and the old semantics are used.* If both the old and the new CLI fail to parse then the error message for the new CLI is emitted.Note that this doesn't add up to a perfect transition. The hope is thatmost of the major cases of change at the very least have somethingprinted. My plan is to land this on `main` and then backport it to the14.0.0 branch as a 14.0.3 release.* Wordsmith messages* Update messages* More wording updates* Fix grammar* More updates List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

d86afc02 - Gate many CLI/Wasmtime features behind Cargo features (#7282)

Thu, 19 Oct 2023 18:01:35 +0000

Gate many CLI/Wasmtime features behind Cargo features (#7282)* Move `wasmtime explore` behind a Cargo featureEnable this Cargo feature by default, but enable building the CLIwithout the `explore` subcommand.* Move the `wast` subcommand behind a Cargo feature* Move support for `wat` behind a CLI featureThis was already conditional in crates such as `wasmtime` and this makesit an optional dependency of the CLI as well.* Move CLI cache support behind a Cargo featureAdditionally refactor `wasmtime-cli-flags` to not unconditionally pullin caching support by removing its `default` feature and appropriatelyenabling it from the CLI.* Move `rayon` behind an optional feature* Move `http-body-util` dependency behind `serve` feature* Add a Cargo feature for compiling out log statementsThis sets the static features of `log` and `tracing` to staticallyremove all log statements from the binary to cut down on binary size.* Move logging support behind a Cargo featureEnables statically removing logging support in addition to the previouscompiling out log statements themselves.* Move demangling support behind a Cargo feature* Enable building the CLI without craneliftCompile out the `compile` subcommand for example.* Gate all profiling support behind one feature flagThis commit moves vtune/jitdump support behind a single `profiling`feature flag that additionally includes the guest profiler dependenciesnow too.* Move support for core dumps behind a feature flag* Move addr2line behind a feature* Fix rebase* Document cargo features and a minimal build* Tidy up the source a bit* Rename compile-out-logging* Document disabling logging* Note the host architecture as well* Fix tests* Fix tests* Mention debuginfo stripping* Fix CI configuration for checking features* Fix book tests* Update lock file after rebase* Enable coredump feature by default List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

079ddd4b - Minor logging tweaks (#7242)

Mon, 16 Oct 2023 14:15:05 +0000

Minor logging tweaks (#7242)Some things I noticed from #7239 which are very much not critical but Ifigure might be nice-to-haves:* Move the logging configuration to the `wasmtime-cli-flags` crate with the other logging configuration to keep it in one place.* Remove `pretty_env_logger` since `tracing-subscriber` probably supplants it.* Don't explicitly inherit env vars in tests since that happens automatically with `Command`. List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

f952ff27 - wasmtime-cli: add tracing output on `WASMTIME_LOG` (#7239)

Fri, 13 Oct 2023 23:01:23 +0000

wasmtime-cli: add tracing output on `WASMTIME_LOG` (#7239)* wasmtime cli: install tracing-subscriber, listen to WASMTIME_LOG, log to stderr* enable tracing colors* audit supply chain for tracing subscriber List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

8a88ff6e - Wasi-http: support inbound requests (proxy world) (#7091)

Thu, 28 Sep 2023 22:51:51 +0000

Wasi-http: support inbound requests (proxy world) (#7091)* Move the incoming_handler impl into http_impl* Remove the incoming handler -- we need to use it as a guest export* Start adding a test-programs test for the server side of wasi-http* Progress towards running a server test* Implement incoming-request-method* Validate outparam value* Initial incoming handler test* Implement more of the incoming api* Finish the incoming api implementations* Initial cut at `wasmtime serve`* fix warning* wasmtime-cli: invoke ServeCommand, and add enough stuff to the linker to run trivial test* fix warnings* fix warnings* argument parsing: allow --addr to specify sockaddr* rustfmt* sync wit definitions between wasmtime-wasi and wasmtime-wasi-http* cargo vet: add an import config and wildcard audit for wasmtime-wmemcheck* cargo vet: audit signal-hook-registry* Remove duplicate add_to_linker calls for preview2 interfacesprtest:full* Add a method to finish outgoing responsesCo-authored-by: Adam Foltzer Co-authored-by: Pat Hickey * Mark the result of the incoming_{request,response}_consume methods as own* Explicit versions for http-body and http-body-util* Explicit `serve` feature for the `wasmtime serve` command* Move the spawn outside of the future returned by `ProxyHandler::call`* Review feedback---------Co-authored-by: Trevor Elliott Co-authored-by: Adam Foltzer List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

f7d0e870 - Require Wasmtime options come before wasm modules (#6946)

Wed, 13 Sep 2023 18:44:36 +0000

Require Wasmtime options come before wasm modules (#6946)This commit implements a new behavior for the CLI of the `wasmtime`executable which will require that options for Wasmtime itself comebefore the wasm module being run. Currently they're allowed to comeafterwards, but instead all arguments and flags coming after a modulewill be interpreted as arguments for the module itself.This feature has a bit of a storied history at this point, and thebreadcrumbs are:* Originally landed in #6737* Reverted for 12.0.0 in #6830* Reverted for 13.0.0 in #6944This PR is intended to be landed as a sibling of #6925, anotherindependent overhaul of Wasmtime's own options on the CLI, for theWasmtime 14.0.0 release. More information about the motivation for thischange, as well as consequences of the fallout, can be found on #6737. List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

df8d3698 - Partially revert CLI argument changes from #6737 (#6944)

Thu, 31 Aug 2023 18:12:37 +0000

Partially revert CLI argument changes from #6737 (#6944)* Partially revert CLI argument changes from #6737This commit is a partial revert of #6737. That change was revertedin #6830 for the 12.0.0 release of Wasmtime and otherwise it's currentlyslated to get released with the 13.0.0 release of Wasmtime. Discussionat today's Wasmtime meeting concluded that it's best to couple thischange with #6925 as a single release rather than spread out acrossmultiple releases. This commit is thus the revert of #6737, althoughit's a partial revert in that I've kept many of the new tests added toshowcase the differences before/after when the change lands.This means that Wasmtime 13.0.0 will exhibit the same CLI behavior as12.0.0 and all prior releases. The 14.0.0 release will have both a newCLI and new argument passing semantics. I'll revert this revert (akare-land #6737) once the 13.0.0 release branch is created and `main`becomes 14.0.0.* Update release notes List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs

80915565 - Require wasmtime options are first when running modules (#6737)

Thu, 20 Jul 2023 13:24:35 +0000

Require wasmtime options are first when running modules (#6737)* Require wasmtime options are first when running modulesCurrently the way we've configured argument parsing it's valid toexecute a command such as: wasmtime run foo.wasm -Owhich is the same as: wasmtime run -O foo.wasmor otherwise all flags are attempted to be parsed as Wasmtime flags andan error is generated when they're not wasmtime flags. I've personallyfound this a bit confusing in the past and I find myself frequentlyexecuting: wasmtime run -- foo.wasm -other -argumentsWhile this works my general impression is that many other "wrappercommands" don't behave this way and typically don't require `--` to passflags to the target executable. This commit reconfigures argumentparsing to consider any argument after the WebAssembly module itself tobe an argument to the wasm program rather than an argument to Wasmtime.This means that all Wasmtime options must come between the `run` commandand the `foo.wasm` WebAssembly argument.* Update wasi testsuite runner* Support `wasmtime -- run`Additionally use more clap features to avoid manually checking againstsubcommands.* Remove stale comment* Reorder wasi-nn arguments* Reorder more flags* Fix unused import on Windows* Don't run a stdio test on Windows* Update gdb/lldb tests* Don't assert that the write succeedsprtest:full List of files: /wasmtime-44.0.1/src/bin/wasmtime.rs