Changes in commands.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/commands.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/commands.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/commands.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/commands.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/commands.rs

9ed441e6 - Introduce the `wasmtime-explorer` crate (#5975)

Sat, 11 Mar 2023 00:33:06 +0000

Introduce the `wasmtime-explorer` crate (#5975)This implements Godbolt Compiler Explorer-like functionality for Wasmtime andCranelift. Given a Wasm module, it compiles the module to native code and thenwrites a standalone HTML file that gives a split pane view between the WAT andASM disassemblies. List of files: /wasmtime-44.0.1/src/commands.rs

8ebaaf92 - Remove the `wasmtime wasm2obj` command (#3301)

Wed, 08 Sep 2021 15:40:58 +0000

Remove the `wasmtime wasm2obj` command (#3301)* Remove the `wasmtime wasm2obj` command This commit removes the `wasm2obj` subcommand of the `wasmtime` CLI. This subcommand has a very long history and dates back quite far. While it's existed, however, it's never been documented in terms of the output it's produced. AFAIK it's only ever been used for debugging to see the machine code output of Wasmtime on some modules. With recent changes to the module serialization output the output of `wasmtime compile`, the `*.cwasm` file, is now a native ELF file which can be fed to standard tools like `objdump`. Consequently I dont think there's any remaining need to keep `wasm2obj` around itself, so this commit removes the subcommand. * More code to delete * Try to fix debuginfo tests List of files: /wasmtime-44.0.1/src/commands.rs

abf3bf29 - Add a `wasmtime settings` command to print Cranelift settings.

Thu, 01 Apr 2021 05:44:13 +0000

Add a `wasmtime settings` command to print Cranelift settings.This commit adds the `wasmtime settings` command to print out availableCranelift settings for a target (defaults to the host).The compile command has been updated to remove the Cranelift ISA options infavor of encouraging users to use `wasmtime settings` to discover what settingsare available. This will reduce the maintenance cost for syncing the compilecommand with Cranelift ISA flags. List of files: /wasmtime-44.0.1/src/commands.rs

29d366db - Add a compile command to Wasmtime.

Thu, 25 Mar 2021 01:49:33 +0000

Add a compile command to Wasmtime.This commit adds a `compile` command to the Wasmtime CLI.The command can be used to Ahead-Of-Time (AOT) compile WebAssembly modules.With the `all-arch` feature enabled, AOT compilation can be performed fornon-native architectures (i.e. cross-compilation).The `Module::compile` method has been added to perform AOT compilation.A few of the CLI flags relating to "on by default" Wasm features have beenchanged to be "--disable-XYZ" flags.A simple example of using the `wasmtime compile` command:```text$ wasmtime compile input.wasm$ wasmtime input.cwasm``` List of files: /wasmtime-44.0.1/src/commands.rs

59258730 - Use structopt instead of docopt.

Tue, 17 Dec 2019 20:38:00 +0000

Use structopt instead of docopt.This commit refactors the Wasmtime CLI tools to use `structopt` instead of`docopt`.The `wasmtime` tool now has the following subcommands:* `config new` - creates a new Wasmtime configuration file.* `run` - runs a WebAssembly module.* `wasm2obj` - translates a Wasm module to native object file.* `wast` - runs a test script file.If no subcommand is specified, the `run` subcommand is used. Thus,`wasmtime foo.wasm` should continue to function as expected.The `wasm2obj` and `wast` tools still exist, but delegate to the sameimplementation as the `wasmtime` subcommands. The standalone `wasm2obj` and`wast` tools may be removed in the future in favor of simply using `wasmtime`.Included in this commit is a breaking change to the default Wasmtimeconfiguration file: it has been renamed from `wasmtime-cache-config.toml` tosimply `config.toml`. The new name is less specific which will allow foradditional (non-cache-related) settings in the future.There are some breaking changes to improve command line UX:* The `--cache-config` option has been renamed to `--config`.* The `--create-config-file` option has moved to the `config new` subcommand.As a result, the `wasm2obj` and `wast` tools cannot be used to create a newconfig file.* The short form of the `--optimize` option has changed from`-o` to `-O` for consistency.* The `wasm2obj` command takes the output object file as arequired positional argument rather than the former required output *option*(e.g. `wasmtime wasm2obj foo.wasm foo.obj`). List of files: /wasmtime-44.0.1/src/commands.rs