Changes in Cargo.toml

46780983 - Exceptions: add exception-specific (command-sequence) fuzzer. (#12923)

Wed, 01 Apr 2026 22:26:11 +0000

Exceptions: add exception-specific (command-sequence) fuzzer. (#12923)* Exceptions: add exception-specific (command-sequence) fuzzer.This fuzzer uses a description of a set of "scenarios", arbitrarilygenerated, to produce a specific kind of module that tests throw/catchbehavior. The module contains a chain of functions that invoke eachother; one will throw, and the rest may have catch clauses that do ordo not catch.* Review feedback. List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

c3a6060b - Polyfill `ToWasmtimeResult` and add eventually-necessary call sites (#12308)

Tue, 13 Jan 2026 18:04:34 +0000

Polyfill `ToWasmtimeResult` and add eventually-necessary call sites (#12308)* Polyfill `ToWasmtimeResult` and add eventually-necessary call sitesThis commit polyfills `wasmtime_internal_error::ToWasmtimeResult` in`wasmtime_environ`, adds the cargo feature plumbing that will eventually connectto the `"wasmtime_internal_error/anyhow"` cargo feature but for now justconfigures this polyfill, and adds uses of the polyfill at all the sites thatwill be necessary once we swap out `anyhow` for`wasmtime_internal_error`. Currently, the polyfill is just an identity function,because `wasmtime::Result`/`wasmtime_environ::error::Result` is just anothername for `anyhow::Result`. Once we do move away from `anyhow`, however, thatwill no longer be the case, and these uses will do the necessary conversion.My goal with landing this as an incremental commit is to make it so that theactual commit that does the error crate swap out can be as close to _just_ the`Cargo.toml` dependency change, without any other code changes as much aspossible. This, in turn, means that swap out should be super easy to revert, ifnecessary.* Add a couple more `.to_wasmtime_result()` invocations in fuzz code* Revert "Add a couple more `.to_wasmtime_result()` invocations in fuzz code"This reverts commit b33696e5f63f7eed731ca9dad10fec5e55a550d3.* Move cranelift fuzz targets back to anyhow* Fix cargo feature enablement for explorer List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

72e909c4 - Migrate fuzzing to `wasmtime::error` (#12269)

Wed, 07 Jan 2026 22:29:30 +0000

Migrate fuzzing to `wasmtime::error` (#12269) List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

b6f59f05 - Split modules (#11993)

Fri, 07 Nov 2025 17:09:47 +0000

Split modules (#11993)* Split GC to different modules and rename table_ops to gc_ops* Remove table_ops from fuzz_targets. Renamed to gc_ops* Address formatting failures List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

6047d27e - Add fuzzer integration for gc/mutatis (#11290)

Mon, 28 Jul 2025 21:05:12 +0000

Add fuzzer integration for gc/mutatis (#11290)* Add fuzzer integration for gc/mutatis* Replace bincode with postcard. Inline fuzz_mutate. Address other small comments* Update Cargo.lock after rebase* Update rng.gen to rng.fill to avoid deprecation failure* Remove table_ops from misc. Update fuzz_target. Keep Arbitrary impl it gives some dependecy error. Will be addressed later* Update Cargo.lock to match upstream/main* Regenerate Cargo.lock after rebase and dependency changes* Reset Cargo.lock to upstream/main to preserve cargo-deny compatibility* Update dependencies---------Co-authored-by: Khagan Karimov List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

ca7081a2 - Consolidate "util" crates for testing (#10423)

Thu, 20 Mar 2025 15:08:47 +0000

Consolidate "util" crates for testing (#10423)* Consolidate "util" crates for testingThis commit consolidates all of the existing crates we have for testinginto a smaller set of crates. Specifically:* `crates/misc/component-fuzz-util` => `wasmtime-test-util` + `component-fuzz` feature* `crates/misc/component-test-util` => `wasmtime-test-util` + `component` feature* `crates/wast-util` => `wasmtime-test-util` + `wast` feature* `crates/misc/component-macro-test` => `wasmtime-test-macros`The goal is to have one location we put various test helpers/macrosrather than our current organically-grown many locations. This isinspired by the test failure on #10405 where I'd like to refactor moreinfrastructure to a "test util" location but it wasn't clear where toput it so I wanted to do this refactoring first.* Remove unused file List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

1ea710d6 - asm: fuzz `cranelift-codegen-x64` in the `misc` target (#10403)

Fri, 14 Mar 2025 23:57:29 +0000

asm: fuzz `cranelift-codegen-x64` in the `misc` target (#10403)As discussed previously, this change adds fuzzing for the x64 assemblerto the melting pot target, `misc`, in order to get at least some fuzzingcycles on OSS-Fuzz. List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

840f5448 - Consolidate some fuzzers into one (#10385)

Wed, 12 Mar 2025 16:57:57 +0000

Consolidate some fuzzers into one (#10385)This commit consolidates a number of fuzzers that we have in Wasmtimeinto a single fuzzer. This follows the pattern of [wasm-tools's `run`fuzzer][tools] where the first byte in the fuzz input says which fuzzerto run and then the rest of the input is the input to the fuzzer. Thisis intended to improve our time-slicing on OSS-Fuzz where less importantfuzzers don't hog time from the "important fuzzers" such as`differential`. Some minor-ish fuzzers have been folded in to this newfuzzer, but we can also always move things around as needed[tools]: https://github.com/bytecodealliance/wasm-tools/blob/main/fuzz/fuzz_targets/run.rs List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

1bb71d31 - Compute dominator tree using semi-NCA algorithm (#9603)

Thu, 09 Jan 2025 16:23:50 +0000

Compute dominator tree using semi-NCA algorithm (#9603)* Add dominator tree computed using semi-NCA algorithm.* Add dominator tree fuzz target* Move previous version of dominator tree to a separate file* Improve comments.* Use the new dominator tree in verifier.* Remove unused `iterators` module. List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

b79a96a1 - Leverage Rust 1.79, 1.80 (#9498)

Tue, 22 Oct 2024 22:00:39 +0000

Leverage Rust 1.79, 1.80 (#9498)This commit is a follow-up to #9496 to leverage various APIs that theworkspace now has access to. For example most dependencies on the`once_cell` crate are now removed in favor of the types stabilized inthe standard library: `LazyLock` and `LazyCell`. One dependency remainsin the `wasmtime` crate due to the `get_or_try_init` not being stableyet.Some additional helper methods on raw pointer slices are also availablefor removing a few minor `unsafe` blocks. List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

c49a1038 - Fix some fuzz issues from updating wasm-tools (#9345)

Tue, 01 Oct 2024 16:06:37 +0000

Fix some fuzz issues from updating wasm-tools (#9345)This commit fixes some fuzz-related issues from the update of the`wasm-tools` family of crates in #9336:* Fuzzing with wasmi disables the GC proposal* The exceptions proposal is always disabled for Wasmtime* Wasmtime conditionally enables the GC/reference-types proposal* Fully disable the GC proposal for now in Wasmtime as its implementation is not complete and fuzzing needs more support.* Log wasm module config before generating to help debug issues like bytecodealliance/wasm-tools#1834 List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

a96845c3 - Fold `cranelift-wasm` crate into `wasmtime-cranelift` (#9313)

Mon, 30 Sep 2024 20:06:43 +0000

Fold `cranelift-wasm` crate into `wasmtime-cranelift` (#9313)This commit removes the `cranelift-wasm` crate by folding it directlyinto the `wasmtime-cranelift` crate. Maintaining a runtime-agnostictranslation of WebAssembly to Cranelift has always been a bit of aburden on us and at this time there are no known users of this cratewho are helping us to maintain this crate. There's a good number ofabstractions in the crate purely for supporting alternative runtimes andthe crate could be much simpler with far less boilerplate if it werespecialized to Wasmtime.This commit purely moves the crate sources, deletes then-dead code, andupdates `use` paths to all point to the right place. Otherwise this doesnot actually yet contain any refactoring to specialize the translationphase to Wasmtime itself. It's expected that will come in follow-upcommits should we decide to merge this. List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

83029e3f - Add `rust-version.workspace = true` to all crates (#9112)

Mon, 12 Aug 2024 15:52:11 +0000

Add `rust-version.workspace = true` to all crates (#9112)Right now this is only on some crates such as `wasmtime` itself and`wasmtime-cli`, but by applying it to all crates it helps with versionselection of those using just Cranelift for example. List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

4ac1bedf - Introduce the `pulley-interpreter` crate (#9008)

Thu, 25 Jul 2024 21:49:26 +0000

Introduce the `pulley-interpreter` crate (#9008)* Introduce the `pulley-interpreter` crateThis commit is the first step towards implementinghttps://github.com/bytecodealliance/rfcs/pull/35This commit introduces the `pulley-interpreter` crate which contains the Pulleybytecode definition, encoder, decoder, disassembler, and interpreter.This is still very much a work in progress! It is expected that we will tweakencodings and bytecode definitions, that we will overhaul the interpreter (to,for example, optionally support the unstable Rust `explicit_tail_calls`feature), and otherwise make large changes. This is just a starting point to getthe ball rolling.Subsequent commits and pull requests will do things like add the Craneliftbackend to produce Pulley bytecode from Wasm as well as the runtime integrationto run the Pulley interpreter inside Wasmtime.* remove stray fn main* Add small tests for special x registers* Remove now-unused import* always generate 0 pc rel offsets in arbitrary* Add doc_auto_cfg feature for docs.rs* enable all optional features for docs.rs* Consolidate `BytecodeStream::{advance,get1,get2,...}` into `BytecodeStream::read`* fix fuzz targets build* inherit workspace lints in pulley's fuzz crate* Merge fuzz targets into one target; fix a couple small fuzz bugs* Add Pulley to our cargo vet config* Add pulley as a crate to publish* Move Pulley fuzz target into top level fuzz directory List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

9f66134e - Resolve aliases before inserting values into the live set (#8945)

Fri, 12 Jul 2024 17:10:37 +0000

Resolve aliases before inserting values into the live set (#8945)* Refactor the internals of `FunctionBuilder::insert_safepoint_spills` into a few smaller methods* Initialize a logger for the `cranelift-fuzzgen` fuzz target* Resolve aliases before inserting values into the live setThis fixes a fuzz bug found in the development ofhttps://github.com/bytecodealliance/wasmtime/pull/8941 List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

7a37e313 - Add a fuzz target for exercising bounds checks with various memory configs (#8742)

Thu, 06 Jun 2024 13:47:19 +0000

Add a fuzz target for exercising bounds checks with various memory configs (#8742) List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

b4ecea38 - Add a fuzzer for async wasm (#8440)

Tue, 23 Apr 2024 19:18:09 +0000

Add a fuzzer for async wasm (#8440)* Add a fuzzer for async wasmThis commit revives a very old branch of mine to add a fuzzer forWasmtime in async mode. This work was originally blocked onllvm/llvm-project#53891 and while that's still an issue it now containsa workaround for that issue. Support for async fuzzing required a gooddeal of refactorings and changes, and the highlights are:* The main part is that new intrinsics, `__sanitizer_{start,finish}_fiber_switch` are now invoked around the stack-switching routines of fibers. This only works on Unix and is set to only compile when ASAN is enabled (otherwise everything is a noop). This required refactoring of things to get it all in just the right way for ASAN since it appears that these functions not only need to be called but more-or-less need to be adjacent to each other in the code. My guess is that while we're switching ASAN is in a "weird state" and it's not ready to run arbitrary code.* Stacks are a problem. The above issue in LLVM outlines how stacks cannot be deallocated at this time because if the deallocated virtual memory is later used for the heap then ASAN will have a false positive about stack overflow. To handle this stacks are specially handled in asan mode by using a special allocation path that never deallocates stacks. This logic additionally applies to the pooling allocator which uses a different stack allocation strategy with ASAN.With all of the above a new fuzzer is added. This fuzzer generates anarbitrary module, selects an arbitrary means of async (e.g.epochs/fuel), and then tries to execute the exports of the module withvarious values. In general the fuzzer is looking for crashes/panics asopposed to correct answers as there's no oracle here. This is alsointended to stress the code used to switch on and off stacks.* Fix non-async build* Remove unused import* Review comments* Fix compile on MIRI* Fix Windows build List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

1898b8c7 - Run all `*.wast` tests in fuzzing (#8121)

Wed, 13 Mar 2024 20:39:03 +0000

Run all `*.wast` tests in fuzzing (#8121)* Run all `*.wast` tests in fuzzingCurrently we have a `spectest` fuzzer which uses fuzz input to generatean arbitrary configuration for Wasmtime and then executes the spec test.This ensures that no matter the configuration Wasmtime can pass spectests. This commit expands this testing to include all `*.wast` tests wehave in this repository. While we don't have a ton we still have somesignificant ones like in #8118 which will only reproduce when turningknobs on CPU features.* Fix CLI build* Fix wast testing List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

04c03b31 - Update the wasm-tools family of crates (#7921)

Mon, 12 Feb 2024 23:22:16 +0000

Update the wasm-tools family of crates (#7921)* Update the wasm-tools family of cratesPulling in some updates to improve how WIT is managed in thisrepository. No changes just yet, however, just pulling in the updatesfirst.* Fix tests* Fix fuzzer build List of files: /wasmtime-44.0.1/fuzz/Cargo.toml

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/fuzz/Cargo.toml