Changes in lib.rs

dbbae440 - Migrate `crates/bench-api` to `wasmtime::error` instead of `anyhow` (#12258)

Wed, 07 Jan 2026 21:12:57 +0000

Migrate `crates/bench-api` to `wasmtime::error` instead of `anyhow` (#12258) List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

4ac219fd - Rename "preview{0,1}" in `wasmtime-wasi` to "p{0,1}" (#11380)

Tue, 05 Aug 2025 18:48:22 +0000

Rename "preview{0,1}" in `wasmtime-wasi` to "p{0,1}" (#11380)* Rename "preview{0,1}" in `wasmtime-wasi` to "p{0,1}"This commit renames the `preview1` module and features to `p1` and doesthe same for `preview0`. This additionally cleans up the test suite abit to share more code amongst all the implementaitons and to also movethe p1 tests out of the p2 folder.This additionally adds a `p2` feature to the `wasmtime-wasi` crate butit does not currently gate the `p2` module because that'll require somemore refactoring an annotations to get that working.* Fix build of the CLI* Fix build of the C API* Fix bench-api build* Fix build of examples* More renamings List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

f7a5aa34 - Unify WASIp{2,3} context structures (#11370)

Sat, 02 Aug 2025 00:57:09 +0000

Unify WASIp{2,3} context structures (#11370)This removes `wasmtime_wasi::p{2,3}::{WasiCtx, WasiCtxBuilder,WasiView}` in favor of only having `wasmtime_wasi::{WasiCtx,WasiCtxBuilder, WasiView}` instead. Conceptually these revisions of WASIall provide the same functionality just with a different veneer that thecomponent model offers, so having only one way to configure host-sidebehavior will make it easier to both organize implementations internally(e.g. more sharing of code) as well as for embedders to configure (onlyone context to create/manage). List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

90ac295e - Update Wasmtime to the 2024 Rust Edition (#10806)

Mon, 19 May 2025 16:40:55 +0000

Update Wasmtime to the 2024 Rust Edition (#10806)* Update Wasmtime to the 2024 Rust EditionNow that our MSRV supports the 2024 edition it's possible to make thisswitch. This commit moves Wasmtime to the 2024 Edition to keepup-to-date with Rust idioms and access many of the edition featuresexclusive to the 2024 edition.prtest:full* Reformat with the 2024 edition List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

2cd52b76 - Allow creation of a CacheConfig without loading from a file (#10665)

Tue, 29 Apr 2025 14:50:26 +0000

Allow creation of a CacheConfig without loading from a file (#10665)* cache: Add builder pattern for CacheConfig* wasmtime: Add cache_config method to wasmtime::Config* Refactor test_builder_default to use test_prolog helper* Remove enabled option from CacheConfigBuilder and always set to true* Change builder methods to take &mut self and return &mut Self* Simplify cache configuration APIA new `cache_config(Option)` method replaces multiple methodsfor controlling module caching. Now `None` disables caching, and users candirectly provide a cache config or load one from a file.* Make cache configuration optional* Add Cache struct to separate configuration from runtime (wip)* Ensure default values earlier* Consolidate CacheConfig and CacheConfigBuilder* Set Cache directly on wastime::Config and make it easier to create onefrom a file* Validate after loading file again* Move cache to top-level module* Fix tests List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

ae84e6ed - Enable `unsafe-attr-outside-unsafe` 2024 edition lint (#9964)

Thu, 09 Jan 2025 21:05:55 +0000

Enable `unsafe-attr-outside-unsafe` 2024 edition lint (#9964)* Enable `unsafe-attr-outside-unsafe` 2024 edition lintThis commit enables the `unsafe-attr-outside-unsafe` lint in rustc usedin transitioning to the 2024 edition. This requires that the`#[no_mangle]` attribute is replaced in favor of `#[unsafe(no_mangle)]`.This mostly affects the C API of wasmtime and most of the changes hereare a simple search/replace.* Another attribute update* Fix command adapter build List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

d621b453 - Bench API: Enable Pulley and allow recompiling with the same bench engine (#9877)

Fri, 20 Dec 2024 16:03:34 +0000

Bench API: Enable Pulley and allow recompiling with the same bench engine (#9877)* bench-api: Allow recompiling with the same engine* Enable Pulley in the bench API List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

57cd5a9e - Start plumbing the ability to run Pulley in Wasmtime (#9646)

Thu, 21 Nov 2024 19:50:51 +0000

Start plumbing the ability to run Pulley in Wasmtime (#9646)* Start plumbing the ability to run Pulley in WasmtimeThis commit starts setting up some infrastructure to run Pulley modulesin Wasmtime, for example on the CLI. This doesn't actually work just yetdue to other missing pieces of integration but this is enough to get toa fault and/or other compiler errors at this time. The changes here are:* An `Engine` allows mismatching targets in the case of Pulley, but the pointer widths must match.* All subcommands of Wasmtime now support `--target`, e.g. `wasmtime run`, as previously only the host was allowed.* Fix compile of bench-api* Fix miri tests* Switch from `NativeEndian` to `Endianness`This switches parsing ELF from always using the native endianness toinstead using a runtime-defined value of endianness. This enablesbig-endian platforms such as s390x to load objects produced for pulley,a little-endian platform. List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

a0442ea0 - Enforce `uninlined_format_args` for the workspace (#9065)

Mon, 05 Aug 2024 09:59:59 +0000

Enforce `uninlined_format_args` for the workspace (#9065)* Enforce `uninlined_format_args` for the workspace* fix: failing `Monolith Checks` job* fix: formatting List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

0f4ae88a - wasi-nn: use resources (#8873)

Thu, 27 Jun 2024 19:14:03 +0000

wasi-nn: use resources (#8873)* wasi-nn: use resourcesRecent discussion in the wasi-nn proposal (see [wasi-nn#59], e.g.) hasconcluded that the right approach for representing wasi-nn "things"(tensors, graph, etc.) is with a component model _resource_. Thissweeping change brings Wasmtime's implementation in line with thatdecision.Initially I had structured this PR to remove all of the WITX-basedimplementation (#8530). But, after consulting in a Zulip [thread] onwhat other WASI proposals aim to do, this PR pivoted to support _both_`the WITX-based and WIT-based ABIs (e.g., preview1 era versus preview2,component model era). What is clear is that the WITX-based specificationwill remain "frozen in time" while the WIT-based implementation movesforward.What that means for this PR is a "split world" paradigm. In many places,we have to distinguish between the `wit` and `witx` versions of the samething. This change isn't the end state yet: it's a big step forwardtowards bringing Wasmtime back in line with the WIT spec but, despite mybest efforts, doesn't fully fix all the TODOs left behind over severalyears of development. I have, however, taken the liberty to refactor andfix various parts as I came across them (e.g., the ONNX backend). I planto continue working on this in future PRs to figure out a good errorparadigm (the current one is too wordy) and device residence.[wasi-nn#59]: https://github.com/WebAssembly/wasi-nn/pull/59[thread]: https://bytecodealliance.zulipchat.com/#narrow/stream/219900-wasi/topic/wasi-nn's.20preview1.20vs.20preview2.20timelineprtest:full* vet: audit `ort`-related crate updates* Simplify `WasiNnView`With @alexcrichton's help, this change removes the `trait WasiNnView`and `struct WasiNnImpl` wrapping that the WIT-based implementation usedfor accessing the host context. Instead, `WasiNnView` is now a `struct`containing the mutable references it needs to make things work. Thisunwraps one complex layer of abstraction, though it does have thedownside that it complicates CLI code to split borrows of `Host`.* Temporarily disable WIT check* Refactor errors to use `trappable_error_type`This change simplifies the return types of the host implementations ofthe WIT-based wasi-nn. There is more work to be done with errors, e.g.,to catch up with the upstream decision to return errors as resources.But this is better than the previous mess. List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

dc1d128a - Respect pooling allocation options in `wasmtime serve` (#8525)

Fri, 03 May 2024 19:47:22 +0000

Respect pooling allocation options in `wasmtime serve` (#8525)* Respect pooling allocation options in `wasmtime serve`This commit updates the processing of pooling allocator options in`wasmtime serve`. Previously the pooling allocator was enabled bydefault but the options to configure it weren't processed due to howthis default-enable was implemented. The option to enable it by defaultfor `wasmtime serve`, but only `wasmtime serve`, is now processeddifferently in a way that handles various otherpooling-allocator-related options.Closes #8504* Fix compile of bench api* Fix test build* Ignore newly added test as it's flaky List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

2b00a541 - Make wasi-common self-contained, deprecate exports from wasmtime-wasi (#7881)

Tue, 13 Feb 2024 17:57:58 +0000

Make wasi-common self-contained, deprecate exports from wasmtime-wasi (#7881)* WIP: try to make wasi-common self contained.* rebase: cargo.lock* remove all dependencies between wasi-common and wasmtime-wasi* use wasi-common directly throughout tests, benches, examples, cli run* wasi-threads: use wasi-common's maybe_exit_on_error in spawned threadnot a very modular design, but at this point wasi-common andwasi-threads are forever wed* fix wasmtime's docs* re-introduce wasmtime-wasi's exports of wasi-common definitions behind deprecated* factor out determining i32 process exit codeand remove libc dep because rustix provides the same constant* commands/run: inline the logic about aborting on trapsince this is the sole place in the codebase its used* Add high-level summary to wasi-common's top-level doc comment.* c-api: fix use of wasi_cap_std_sync => wasi_common::sync, wasmtime_wasi => wasi_common* fix tokio example* think better of combining downcast and masking into one method* fix references to wasmtime_wasi in docsprtest:full* benches: use wasi-common* cfg-if around use of rustix::process because that doesnt exist on windows* wasi-common: include tests, caught by verify-publish* fix another bench* exit requires wasmtime dep. caught by verify-publish. List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

85c0a2df - Switch to simpler fuel APIs (#7298)

Mon, 23 Oct 2023 19:50:23 +0000

Switch to simpler fuel APIs (#7298)In an effort to simplify the many fuel related APIs, simplify theinterface here to a single counter with get and set methods.Additionally the async yield is reduced to an interval of the total fuelinstead of injecting fuel, so it's easy to still reason about how muchfuel is left even with yielding turned on.Internally this works by keeping two counters - one the VM uses toincrement towards 0 for fuel, the other to track how much is in"reserve". Then when we're out of gas, we pull from the reserve torefuel and continue. We use the reserve in two cases: one for overflowof the fuel (which is an i64 and the API expresses fuel as u64) and theother for async yieling, which then the yield interval acts as a cap tohow much we can refuel with.This also means that `get_fuel` can return the full range of `u64`before this change it could only return up to `i64::MAX`. This isimportant because this PR is removing the functionality to track fuelconsumption, and this makes the API less error prone for embedders totrack consumption themselves.Careful to note that the VM counter that is stored as `i64` can bepositive if an instruction "costs" multiple units of fuel when the fuelran out.prtest:fullSigned-off-by: Tyler Rockwood List of files: /wasmtime-44.0.1/crates/bench-api/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/crates/bench-api/src/lib.rs

6084b736 - Fix build of `wasmtime-wasi-bench` (#6999)

Mon, 11 Sep 2023 17:10:31 +0000

Fix build of `wasmtime-wasi-bench` (#6999)Looks like this wasn't built on CI since it wasn't tested. Flag it astestable which should build it on CI which should catch future errorslike this. List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

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/crates/bench-api/src/lib.rs

cd93f17a - wasmtime bench-api build error when using --feature wasi-crypto (#6670) (#6671)

Thu, 29 Jun 2023 15:13:50 +0000

wasmtime bench-api build error when using --feature wasi-crypto (#6670) (#6671)Fixing typo of wasmtime_wasi_nn -> wasmtime_wasi_crypto that was causinga build error when building the bench-api with the wasi-crypto featureenabled. List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

a491eaca - Ability to disable cache after it's been configured on `Config` (#5542)

Fri, 06 Jan 2023 21:12:59 +0000

Ability to disable cache after it's been configured on `Config` (#5542)* Wasmtime: Add `Config::disable_cache` * bench-api: Always disable the cache * bench-api: Always get a `Config` from CLI flags This commit fixes an issue that I ran into just now where benchmarking one `*.so` with `--engine-flags` was giving wildly unexpected results comparing to something without `--engine-flags`. The root cause here appears to that when specifying `--engine-flags` the CLI parsing code is used to create a `Config` and when omitted a `Config::new` instance is created. The main difference between these is that for the CLI caching is enabled by default and for `Config::new` it is not. Coupled with the fact that caching doesn't really work for the `main` branch this ended up giving wild results. The fix here is to first always use the CLI parsing code to create a `Config` to ensure that a config is consistently created. Next the `--disable-cache` flag is unconditionally passed to the CLI parsing to ensure that compilation actually happens. Once applied this enables comparing an engine without flags and an engine with flags which provides consistent results. * Fix compile error Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

2cfa0248 - Support fuel and epoch interruption in the benchmarking API (#5449)

Thu, 15 Dec 2022 22:56:16 +0000

Support fuel and epoch interruption in the benchmarking API (#5449)When these engine flags are passed be sure to configure the store appropriately to ensure that the wasm can actually run instead of crashing immediately, enabling benchmarking comparisons between these modes. List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs

1bd78f1a - Fix get_typed_fund extra param in benchmark (#5280)

Wed, 16 Nov 2022 14:56:03 +0000

Fix get_typed_fund extra param in benchmark (#5280) List of files: /wasmtime-44.0.1/crates/bench-api/src/lib.rs