Changes in compile_time_builtins.rs

7a4f53a3 - Fix build without `wat` feature. (#12706)

Wed, 04 Mar 2026 22:32:10 +0000

Fix build without `wat` feature. (#12706)Signed-off-by: Piotr Sikora List of files: /wasmtime-44.0.1/crates/wasmtime/src/compile/code_builder/compile_time_builtins.rs

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/crates/wasmtime/src/compile/code_builder/compile_time_builtins.rs

ff33e949 - Do not re-export `anyhow!` in the `wasmtime::prelude` (#12298)

Fri, 09 Jan 2026 19:23:56 +0000

Do not re-export `anyhow!` in the `wasmtime::prelude` (#12298)We are trying to move to `format_err!` instead. List of files: /wasmtime-44.0.1/crates/wasmtime/src/compile/code_builder/compile_time_builtins.rs

e069bdd3 - `CodeBuilder` APIs for defining compile-time builtins (#11918)

Thu, 23 Oct 2025 18:46:59 +0000

`CodeBuilder` APIs for defining compile-time builtins (#11918)* `CodeBuilder` APIs for defining compile-time builtinsCompile-time builtins, as described in [theRFC](https://github.com/bytecodealliance/rfcs/blob/main/accepted/wasmtime-compile-time-builtins.md),are effectively the sum of three parts:1. Function inlining2. Unsafe intrinsics3. Component compositionThe first two have already been implemented in Wasmtime. This commit implementsthe final part, leveraging `wasm-compose` to link host-defined compile-timebuiltin components with guest-defined main components. It exposes Wasmtime'sunsafe intrinsics only to the host-defined compile-time builtins, not theguest-defined main Wasm component.Why `wasm-compose` and not `wac`? Because it is in the same repo as the rest ofthe `wasm-tools` crates, and therefore it is easy to depend on without bringingin duplicate copies of that family of crates into our workspace and builds. Alsoits programmatic API is somewhat easier to use, and is not spread acrossmultiple crates.* Fix unused lifetime in `cfg(not(feature = "compile-time-builtins"))`* Fix an unused warning when `cfg(not(feature = "compile-time-builtins"))`* Add cargo vet audit for `fixedbitset` version `0.4.2`* Add cargo vet audit for `bitmaps` version 2.10.0* Add cargo vet audit for `sized-chunks` diff `0.6.5 -> 0.7.0`* Add/tweak cargo vet exemptions for some depsThese all have >10,000 daily downloads, and so are okay to exempt per ourpolicy:https://docs.wasmtime.dev/contributing-coding-guidelines.html#policy-for-adding-cargo-vet-entries* Add cargo vet audit for `wasm-compose` diff `0.236.0 -> 0.238.1`Don't know why I have to do this certification even though we have a wildcardaudit for this crate because it is authored by the Bytecode Alliance...* Fix visibility of type* Move compile-time builtins methods to module to cut down on `cfg`s* Skip checking `heck` in `cargo deny`Until https://github.com/bytecodealliance/wasm-tools/pull/2359 is merged,released, and updated in this tree.* Always read compile-time inputs* Tighten up parse loop and level tracking* as_deref instead of clone* Remove 'b lifetime from CodeBuilder* fix `cfg(not(feature = "compile-time-builtins"))` build* Ignore tests that run wasm when in MIRI List of files: /wasmtime-44.0.1/crates/wasmtime/src/compile/code_builder/compile_time_builtins.rs