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

ed7eb500 - Require lint reasons in `wasmtime-cli` (#10175)

Mon, 03 Feb 2025 19:15:08 +0000

Require lint reasons in `wasmtime-cli` (#10175)Continuation of #9696 List of files: /wasmtime-44.0.1/src/lib.rs

45b60bd6 - Start using `#[expect]` instead of `#[allow]` (#9696)

Mon, 02 Dec 2024 17:19:20 +0000

Start using `#[expect]` instead of `#[allow]` (#9696)* Start using `#[expect]` instead of `#[allow]`In Rust 1.81, our new MSRV, a new feature was added to Rust to use`#[expect]` to control lint levels. This new lint annotation willsilence a lint but will itself cause a lint if it doesn't actuallysilence anything. This is quite useful to ensure that annotations don'tget stale over time.Another feature is the ability to use a `reason` directive on theattribute with a string explaining why the attribute is there. Thisstring is then rendered in compiler messages if a warning or errorhappens.This commit migrates applies a few changes across the workspace:* Some `#[allow]` are changed to `#[expect]` with a `reason`.* Some `#[allow]` have a `reason` added if the lint conditionally fires (mostly related to macros).* Some `#[allow]` are removed since the lint doesn't actually fire.* The workspace configures `clippy::allow_attributes_without_reason = 'warn'` as a "ratchet" to prevent future regressions.* Many crates are annotated to allow `allow_attributes_without_reason` during this transitionary period.The end-state is that all crates should use`#[expect(..., reason = "...")]` for any lint that unconditionally firesbut is expected. The `#[allow(..., reason = "...")]` lint should be usedfor conditionally firing lints, primarily in macro-related code.The `allow_attributes_without_reason = 'warn'` level is intended to bepermanent but the transitionary`#[expect(clippy::allow_attributes_without_reason)]` crate annotationsto go away over time.* Fix adapter buildprtest:full* Fix one-core build of icache coherence* Use `allow` for missing_docsWork around rust-lang/rust#130021 which was fixed in Rust 1.83 and isn'tfixed for our MSRV at this time.* More MSRV compat List of files: /wasmtime-44.0.1/src/lib.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/lib.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/lib.rs

5856590f - Configure workspace lints, enable running some Clippy lints on CI (#7561)

Mon, 20 Nov 2023 23:23:41 +0000

Configure workspace lints, enable running some Clippy lints on CI (#7561)* Configure Rust lints at the workspace levelThis commit adds necessary configuration knobs to have lints configuredat the workspace level in Wasmtime rather than the crate level. Thisuses a feature of Cargo first released with 1.74.0 (last week) of the`[workspace.lints]` table. This should help create a more consistent setof lints applied across all crates in our workspace in addition topossibly running select clippy lints on CI as well.* Move `unused_extern_crates` to the workspace levelThis commit configures a `deny` lint level for the`unused_extern_crates` lint to the workspace level rather than theprevious configuration at the individual crate level.* Move `trivial_numeric_casts` to workspace level* Change workspace lint levels to `warn`CI will ensure that these don't get checked into the codebase andotherwise provide fewer speed bumps for in-process development.* Move `unstable_features` lint to workspace level* Move `unused_import_braces` lint to workspace level* Start running Clippy on CIThis commit configures our CI to run `cargo clippy --workspace` for allmerged PRs. Historically this hasn't been all the feasible due to theamount of configuration required to control the number of warnings onCI, but with Cargo's new `[lint]` table it's possible to have aone-liner to silence all lints from Clippy by default. This commit bydefault sets the `all` lint in Clippy to `allow` to by-default disablewarnings from Clippy. The goal of this PR is to enable selective accessto Clippy lints for Wasmtime on CI.* Selectively enable `clippy::cast_sign_loss`This would have fixed #7558 so try to head off future issues with thatby warning against this situation in a few crates. This lint is stillquite noisy though for Cranelift for example so it's not worthwhile atthis time to enable it for the whole workspace.* Fix CI errorprtest:full List of files: /wasmtime-44.0.1/src/lib.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/lib.rs

993e26e0 - wasmtime: Handle common cli args in `wasmtime serve` (#7134)

Wed, 04 Oct 2023 19:15:56 +0000

wasmtime: Handle common cli args in `wasmtime serve` (#7134)* Refactor option handling in the `run` and `serve` commands* Use a real thread to manage epoch increments* Move module/component loading into src/common.rs* Require wasi-http and component-model to not be disabled in serve List of files: /wasmtime-44.0.1/src/lib.rs

8995750a - Redesign Wasmtime's CLI (#6925)

Mon, 11 Sep 2023 22:05:35 +0000

Redesign Wasmtime's CLI (#6925)* Redesign Wasmtime's CLIThis commit follows through on discussion from #6741 to redesign theflags that the `wasmtime` binary accepts on the CLI. Almost all flagshave been renamed/moved and will require callers to update. The mainmotivation here is to cut down on the forest of options in `wasmtime -h`which are difficult to mentally group together and understand.The main change implemented here is to move options behind "optiongroups" which are intended to be abbreviated with a single letter:* `-O foo` - an optimization or performance-tuning related option* `-C foo` - a codegen option affecting the compilation process.* `-D foo` - a debug-related option* `-W foo` - a wasm-related option, for example changing wasm semantics* `-S foo` - a WASI-related option, configuring various proposals for exampleEach option group can be explored by passing `help`, for example `-Ohelp`. This will print all options within the group along with theirhelp message. Additionally `-O help-long` can be passed to print thefull comment for each option if desired.Option groups can be specified multiple times on the command line, forexample `-Wrelaxed-simd -Wthreads`. They can also be combined togetherwith commas as `-Wrelaxed-simd,threads`. Configuration works as a "lastoption wins" so `-Ccache,cache=n` would end up with a compilationcache disabled.Boolean options can be specified as `-C foo` to enable `foo`, or theycan be specified with `-Cfoo=$val` with any of `y`, `n`, `yes`, `no`,`true`, or `false`. All other options require a `=foo` value to bepassed and the parsing depends on the type.This commit additionally applies a few small refactorings to the CLI aswell. For example the help text no longer prints information about wasmfeatures after printing the option help. This is still available via`-Whelp` as all wasm features have moved from `--wasm-features` to `-W`.Additionally flags are no longer conditionally compiled in, but insteadall flags are always supported. A runtime error is returned if supportfor a flag is not compiled in. Additionally the "experimental" name ofWASI proposals has been dropped in favor of just the name of theproposal, for example `--wasi nn` instead of `--wasi-modulesexperimental-wasi-nn`. This is intended to mirror how wasm proposalsdon't have "experimental" in the name and an opt-in is requiredregardless.A full listing of flags and how they have changed is:| old cli flag | new cli flag ||-----------------------------------------------|-------------------------------------------------|| `-O, --optimize` | removed || `--opt-level ` | `-O opt-level=N` || `--dynamic-memory-guard-size ` | `-O dynamic-memory-guard-size=...` || `--static-memory-forced` | `-O static-memory-forced` || `--static-memory-guard-size ` | `-O static-memory-guard-size=N` || `--static-memory-maximum-size ` | `-O static-memory-maximum-size=N` || `--dynamic-memory-reserved-for-growth ` | `-O dynamic-memory-reserved-for-growth=...` || `--pooling-allocator` | `-O pooling-allocator` || `--disable-memory-init-cow` | `-O memory-init-cow=no` || `--compiler ` | `-C compiler=..` || `--enable-cranelift-debug-verifier` | `-C cranelift-debug-verifier` || `--cranelift-enable ` | `-C cranelift-NAME` || `--cranelift-set ` | `-C cranelift-NAME=VALUE` || `--config ` | `-C cache-config=..` || `--disable-cache` | `-C cache=no` || `--disable-parallel-compilation` | `-C parallel-compilation=no` || `-g` | `-D debug-info` || `--disable-address-map` | `-D address-map=no` || `--disable-logging` | `-D logging=no` || `--log-to-files` | `-D log-to-files` || `--coredump-on-trap ` | `-D coredump=..` || `--wasm-features all` | `-W all-proposals` || `--wasm-features -all` | `-W all-proposals=n` || `--wasm-features bulk-memory` | `-W bulk-memory` || `--wasm-features multi-memory` | `-W multi-memory` || `--wasm-features multi-value` | `-W multi-value` || `--wasm-features reference-types` | `-W reference-types` || `--wasm-features simd` | `-W simd` || `--wasm-features tail-call` | `-W tail-call` || `--wasm-features threads` | `-W threads` || `--wasm-features memory64` | `-W memory64` || `--wasm-features copmonent-model` | `-W component-model` || `--wasm-features function-references` | `-W function-references` || `--relaxed-simd-deterministic` | `-W relaxed-simd-deterministic` || `--enable-cranelift-nan-canonicalization` | `-W nan-canonicalization` || `--fuel ` | `-W fuel=N` || `--epoch-interruption` | `-W epoch-interruption` || `--allow-unknown-exports` | `-W unknown-exports-allow` || `--trap-unknown-imports` | `-W unknown-imports-trap` || `--default-values-unknown-imports` | `-W unknown-imports-default` || `--max-instances ` | `-W max-instances=N` || `--max-memories ` | `-W max-memories=N` || `--max-memory-size ` | `-W max-memory-size=N` || `--max-table-elements ` | `-W max-table-elements=N` || `--max-tables ` | `-W max-tables=N` || `--max-wasm-stack ` | `-W max-wasm-stack=N` || `--trap-on-grow-failure` | `-W trap-on-grow-failure` || `--wasm-timeout ` | `-W timeout=N` || `--wmemcheck` | `-W wmemcheck` || `--wasi-modules default` | removed || `--wasi-modules -default` | removed || `--wasi-modules wasi-common` | `-S common` || `--wasi-modules -wasi-common` | `-S common=n` || `--wasi-modules experimental-wasi-nn` | `-S nn` || `--wasi-modules experimental-wasi-threads` | `-S threads` || `--wasi-modules experimental-wasi-http` | `-S http` || `--listenfd` | `-S listenfd` || `--tcplisten ` | `-S tcplisten=...` || `--wasi-nn-graph ` | `-S nn-graph=FORMAT::HOST` || `--preview2` | `-S preview2` || `--dir ` | `--dir ...` || `--mapdir ` | `--dir a::b` |* Be more descriptive with help text* Document `=val` is optional for `-Ccranelift-xxx`* Fix compile after rebase* Fix rebase of `--inherit-network`* Fix wasi-http test* Fix compile without pooling allocator support* Update some flags in docs* Fix bench-api build* Update flags for gdb/lldb tests* Fixup optimization flagsprtest:full List of files: /wasmtime-44.0.1/src/lib.rs

62fdafa1 - Remove clippy configuration from repo and crates (#6927)

Tue, 29 Aug 2023 21:07:27 +0000

Remove clippy configuration from repo and crates (#6927)Wasmtime's CI does not run clippy so there's no enforcement of thisconfiguration. Additionally the configuration per-crate is not uniformlyapplied across all of the Wasmtime workspace and is only on somehistorical crates. Because we don't run clippy in CI this commit removesall of the clippy annotations for allow/warn/deny from the source. List of files: /wasmtime-44.0.1/src/lib.rs

4f84e641 - Revert #131, renaming `main` back to `run`. (#165)

Wed, 03 May 2023 21:51:44 +0000

Revert #131, renaming `main` back to `run`. (#165)Changing LLVM and/or Rust to avoid special handling of `main` is a fair amount of work, and there could be other toolchains with similar special rules for functions named `main`, so rename the command entrypoint back to `run`. We could potentially re-evaluate this in the future, such as in a preview3 timeframe, but for now, let's go with the simplest thing that works. List of files: /wasmtime-44.0.1/src/lib.rs

1e04bf29 - adapter: StreamType::Unknown is actually Stdio (#161)

Wed, 03 May 2023 19:20:41 +0000

adapter: StreamType::Unknown is actually Stdio (#161)We have only ever used Unknown for the stdio streams, and I don't expect us to use it for anything else in the future, so rename it. Set the returned filetype to character device: Closes #146. Also, fix some warnings. List of files: /wasmtime-44.0.1/src/lib.rs

02292601 - adapter poll_oneoff: when descriptors.get_*_stream(fd) fails, die with that error (#154)

Mon, 24 Apr 2023 22:08:42 +0000

adapter poll_oneoff: when descriptors.get_*_stream(fd) fails, die with that error (#154)* adapter poll_oneoff: when descriptors.get_*_stream(fd) fails, die with that error There was a special case in poll_oneoff that put in a fake clock stream when a read/write stream for a descriptor wasn't available. The poll_oneoff_files test (in `test_fd_readwrite_invalid_fd()`) checks that poll_oneoff returns a BADF when an invalid fd is subscribed to. I'm not sure what the special case was patching over, but this passes all of the other tests right now. * poll_oneoff_files fails on windows with god knows what error diff --git a/host/tests/command.rs b/host/tests/command.rs index 7af7bd0..67c8c0b 100644 --- a/host/tests/command.rs +++ b/host/tests/command.rs @@ -466,10 +466,11 @@ async fn run_path_symlink_trailing_slashes(store: Store, wasi: Command) } async fn run_poll_oneoff_files(store: Store, wasi: Command) -> Result<()> { - // trapping upwrap in poll_oneoff in adapter. - // maybe this is related to the "if fd isnt a stream, request a pollable which completes - // immediately so itll immediately fail" behavior, which i think breaks internal invariant... - run_with_temp_dir(store, wasi).await + if cfg!(windows) { + expect_fail(run_with_temp_dir(store, wasi).await) + } else { + run_with_temp_dir(store, wasi).await + } } async fn run_poll_oneoff_stdio(store: Store, wasi: Command) -> Result<()> { List of files: /wasmtime-44.0.1/src/lib.rs

806d23d3 - delete spurrious extra line in adapter (this same var is created below)

Fri, 21 Apr 2023 00:20:39 +0000

delete spurrious extra line in adapter (this same var is created below) List of files: /wasmtime-44.0.1/src/lib.rs

f0ed67a1 - fix bug in adapter fd_fdstat_set_flags to frob the append flag.

Fri, 21 Apr 2023 00:19:48 +0000

fix bug in adapter fd_fdstat_set_flags to frob the append flag.this fixes the fd_flags_set test. List of files: /wasmtime-44.0.1/src/lib.rs

93e4bd16 - NFC, looks more consistient to my eye though

Thu, 20 Apr 2023 22:49:34 +0000

NFC, looks more consistient to my eye though List of files: /wasmtime-44.0.1/src/lib.rs

fddf6ca5 - fd_seek: error with invalid offsets in the adapter

Thu, 20 Apr 2023 22:47:42 +0000

fd_seek: error with invalid offsets in the adapter List of files: /wasmtime-44.0.1/src/lib.rs

b0fed763 - adapter: change logic around interpeting ATIM and ATIM_NOW (and MTIM equiv) to be consistient with upstream

Thu, 20 Apr 2023 19:08:47 +0000

adapter: change logic around interpeting ATIM and ATIM_NOW (and MTIM equiv) to be consistient with upstreamin wasi-common preview1, ATIM and ATIM_NOW (and MTIM and MTIM now) were mutually exclusive and would result in an INVAL error, whereas in the adapter previously, ATIM_NOW implied ATIM, but would silently do nothing if ATIM was not set.I decided to be consistient with the upstream behavior here because it is pretty arbitrary and I don't think there's a good reason to break compatibility.This fixes the `path_filestat` test. List of files: /wasmtime-44.0.1/src/lib.rs

b8018eda - adapter: track blocking state in File, remove uses of set-flags

Thu, 20 Apr 2023 00:21:05 +0000

adapter: track blocking state in File, remove uses of set-flags List of files: /wasmtime-44.0.1/src/lib.rs

4bba05d7 - readlink: fix adapter to return right len, and test to expect truncation

Mon, 17 Apr 2023 22:13:39 +0000

readlink: fix adapter to return right len, and test to expect truncationtruncation behavior is backported to upstream in https://github.com/bytecodealliance/wasmtime/pull/6225 List of files: /wasmtime-44.0.1/src/lib.rs