Changes in function_runner.rs

2283e84f - Fix a panic with a massive `max_wasm_stack` configured (#12869)

Mon, 30 Mar 2026 18:32:56 +0000

Fix a panic with a massive `max_wasm_stack` configured (#12869)* Fix a panic with a massive `max_wasm_stack` configuredThis commit fixes a panic through a `checked_add(...).unwrap()` whichcan happen when `Config::max_wasm_stack` is configured to be a verylarge value. This is a mostly benign panic as it's unlikely this isconfigured much in the wild, but nevertheless seems like a good issuesto fix regardless.* Fix an overflow/OOM panic in pulleyprtest:full* Fix CI* Another CI fix* Fix test on 32-bit* Fix miri test List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

33cbb217 - Avoid `copy_from_slice` in the p1 adapter (#12088)

Wed, 26 Nov 2025 14:47:24 +0000

Avoid `copy_from_slice` in the p1 adapter (#12088)* Avoid `copy_from_slice` in the p1 adapterThis is not fully optimized on nightly where a possible panic pointremains which breaks the build of the adapter, so resort to`ptr::copy_nonverlapping` to avoid this dead panic code.* Fix macos* More macos fixesprtest:full List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

56a6c2d5 - Manually implement libcalls in cranelift-filetests (#11824)

Mon, 13 Oct 2025 20:12:02 +0000

Manually implement libcalls in cranelift-filetests (#11824)* Manually implement libcalls in cranelift-filetestsInstead of relying on the system `libm` to provide the implementation ofthese libcalls through `dlopen` this commit instead changescranelift-filetests to use handwritten implementations of variouslibcalls. This has the primary benefit of ensuring that the sameimplementation is used in both the interpreter and compiled code whenlibcalls are made. This ensure that during differential fuzzing explicitinvocations of libcalls will produce the same result, even with respectto NaN bits, since the implementation is the same (whatever the Ruststandard library does).* Fix mul_add on mingw* Fix build on Windows* Really fix the build this time... List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

3c3fb35b - Clarify docs around exceptions in Cranelift (#11601)

Wed, 03 Sep 2025 20:37:59 +0000

Clarify docs around exceptions in Cranelift (#11601)* Clarify docs around exceptions in CraneliftThis is a result of today's Cranelift meeting with some of my questionsaround the ABI bits here and there. Notably:* Cranelift is audited and now documented to always consider the callee calling convention in `try_call`, disregarding the caller calling convention.* Wasmtime's exception throw now explicitly names the `tailcc` in the name to indicate that it's only compatible with the tail calling convention.* The verifier test for exceptions is expanded with a few more cases here and there that I could think of.* Backends now assert that the size of the calling-convention list of payload types is the same as the size of the list of registers the backend places results into.* Fix a typo List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

789f0374 - Package up exception handler state (#11577)

Wed, 03 Sep 2025 19:07:30 +0000

Package up exception handler state (#11577)* Package up exception handler stateThis commit is a minor refactoring of the `wasmtime-unwinder` crate touse a `Handler` structure as a "package" for the pc/fp/sp triple that'srequired to resume to an exception handler. Freestanding functions are nowassociated methods/functions of `Handler` such as finding a frame on thestack and resuming to a handler.This doesn't actually change any behavior, just moving some thingsaround to prepare for a future refactoring.* Fix some CI issues* Fix conditional build List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

fa1d6867 - Wasmtime/Cranelift: carry "FP to SP offset" in exception data, and use it in stackwalk. (#11500)

Thu, 21 Aug 2025 22:40:47 +0000

Wasmtime/Cranelift: carry "FP to SP offset" in exception data, and use it in stackwalk. (#11500)* Wasmtime/Cranelift: carry "FP to SP offset" in exception data, and use it in stackwalk.Currently Wasmtime unwinds stack frames to look for exception handlersby walking frames one-by-one, following the FP chain as usual, andassuming that *these frames are contiguous*: that is, that the SP inany given frame (bottom of that frame) is immediately above the FP ofthe next lower frame, plus the FP/return address pair (e.g. 16 bytes).This allows us to get the SP for any given frame in addition to FP. Weneed SP for two reasons:- To look up dynamic context, to match Wasm tag instances for handlers against the thrown tag;- To actually set SP when we resume, if we do resume to a handler in this frame.This logic *almost but not quite* worked: I had forgotten that in ourtail-call ABI, we need to clean up incoming stack args in thecallee (because only the final callee in a parade of tail-callingfunctions that reuse the same stack frame location knows how many argsit has, not the original caller). This implies that there is an"incoming args area" *above* the FP/return address pair. Thus, framesare not necessarily contiguous by the above definition.In #11489 we see a case where a function of signature `(func)`tail-calls one of `(func (param i32 i32 i32 i32 i32))`, which onx86-64 (with four arg registers left for Wasm) is sufficient to createincoming stack args, which then trips up the unwinder, reading a bogusvmctx and segfaulting.The most reasonable solution seems to be to embed the SP-to-FP offsetin the exception metadata itself, so from only the FP (which istotally robust -- we rely on the FP chain for multiple kinds ofstack-walking) we can get the SP, allowing us to read dynamic contextand to reset SP during resume.This PR does just that. Technically, in our ABI, the SP-to-FP offsetis constant for an entire function, but it was simpler in theexception metadata to encode this per callsite instead (there is noother notion of "per-function" data, only "per-callsite", so it wouldbe a separate binary search).Fixes #11489.prtest:full* Review feedback. List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

2d25f862 - WebAssembly exception-handling support. (#11326)

Thu, 21 Aug 2025 02:55:44 +0000

WebAssembly exception-handling support. (#11326)* WebAssembly exception-handling support.This PR introduces support for the [Wasm exception-handling proposal],which introduces a conventional try/catch mechanism to WebAssembly. ThePR supports modules that use `try_table` to register handlers for alexical scope; and provides `throw` and `throw_ref` that allocate (inthe first case) and throw exception objects.This PR builds on top of the work in #10510 for Cranelift-levelexception support, #10919 for an unwinder, and #11230 for exceptionobjects built on top of GC, in addition a bunch of smaller fix andenabling PRs around those.[Wasm exception-handling proposal]: https://github.com/WebAssembly/exception-handling/prtest:full* Permit UnwindToWasm to have unused fields in Pulley builds (for now).* Resolve miri-caught reborrowing issue.* Ignore exceptions tests in miri for now (Pulley not supported).* Use wasmtime_test on exceptions tests.* Get tests passing on pulley platforms* Add a check to `supports_host` for the generated test and assert failure also when that is false.* Remove `pulley_unsupported` test as it falls out of `#[wasmtime_test]`* Remove `exceptions_store` helper as it falls out of `#[wasmtime_test]`* Remove miri annotations as they fall out of `#[wasmtime_test]`* Remove dead import* Skip some unsupported tests entirely in `#[wasmtime_test]`If the selected compiler doesn't support the host at all then there's noneed to run it. Actually running it could misinterpret `CraneliftNative`as "run with pulley" otherwise, so avoid such false negatives.* Cranelift: dynamic contexts: account for outgoing-args area.---------Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

69b4acbf - Bump MSRV to Rust 1.87.0 (#11396)

Thu, 07 Aug 2025 21:17:41 +0000

Bump MSRV to Rust 1.87.0 (#11396)* Bump MSRV to Rust 1.87.0Coincides with today's release of Rust 1.89* Fix some lint warnings* Fix tests with Pulley* Fix lldb tests* Fix a doc test on 32-bit List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

8a42768f - Update nightly used in CI (#10957)

Fri, 06 Jun 2025 18:06:28 +0000

Update nightly used in CI (#10957)A new lint was added to rustc so this updates the nightly used in CI andthen additionally fixes the lints that are firing. List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

efa236e5 - Cranelift: implement an "unwinder" crate and exception throws in filetests. (#10919)

Thu, 05 Jun 2025 01:39:23 +0000

Cranelift: implement an "unwinder" crate and exception throws in filetests. (#10919)This commit introduces the next major piece of machinery (after thepreviously-landed `try_call` support) that we will eventually use toimplement Wasm exceptions in Wasmtime. In particular, it implements ageneric unwinder as a new crate that supports (i) walking a stackproduced by Cranelift code, (ii) serializing Cranelift exceptionmetadata to compact tables (in a way very similar to address maps inWasmtime, so they will be mappable directly from disk), (iii) usingthese serialized tables to find handlers during a stack-walk, and (iv)jumping to handlers (i.e., actually unwinding). This crate is currentlyused in the filetests runner, and will next be used in Wasmtime.The commit first performs code-motion: it moves stack-walking code fromWasmtime to `cranelift-unwinder`. This itself has no functional effect,but isolates the code that understands contiguous sequences of Craneliftframes ("activations") from that which is specific to Wasmtime'sactivation delimiters and metadata.It then implements a compact exception-table format. This format usesthe `object` crate's mechanisms for directly referencing in-memoryarrays of little-endian `u32`s in a way that will allow us to findhandlers when mapping exception metadata directly from an ELF section ina `.cwasm` (for example). The format consists of four sorted `u32`arrays in a way that allows us to look up a callsite first, then searchits sorted array of handler offsets by tags.It next implements the actual unwind control flow: it contains anassembly stub for each supported architecture that transfers control toa PC, SP, and FP value "up the stack", with payload values placed in thepayload registers we have defined per our exception ABI in Cranelift.Finally, it puts these pieces together in the filetest runner. Note thatthe runtest does a lot "by hand": we don't have entry and exittrampolines as we do in Wasmtime, so the filetest contains threefunctions, with the middle one invoking the "throw hostcall" and entryand exit trampolines around it grabbing the appropriate entry/exit FPsand exit PC. The dance to call back to host code is also somewhatdelicate, as we haven't done this before. The `JITModule`'s linking +relocation support does not seem sufficient to properly define a symbol,so instead we scan for `func_addr` instructions referencing a well-knownname (`__cranelift_throw`) and replace them with `iconst`s with thefunction address at runtime, baking it in. This is somewhat ugly, but itworks. All of these filetest-specific details will be handled much morenicely in the Wasmtime version of this functionality, as we have properabstractions for entry/exit trampolines and hostcalls. List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.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/cranelift/filetests/src/function_runner.rs

61ba09f6 - Update MSRV to 1.85.0 (#10785)

Mon, 19 May 2025 13:26:20 +0000

Update MSRV to 1.85.0 (#10785)* Update MSRV to 1.85.0This makes us eligible to update to the 2024 Rust edition but I'mplanning on deferring that to a separate follow-up change.prtest:full* Fix unused mut* Try harder to link `cosf` and thus `libm` List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

0ac3e1ec - Update linkage of `libm` for nightly Rust (#10587)

Tue, 15 Apr 2025 19:18:33 +0000

Update linkage of `libm` for nightly Rust (#10587)Upstream rustc has changed meaning that the `ceil` function is nowdefined in bcompiler-builtins, so link a different symbol to forcepulling in `libm` to get `dlsym` working for its symbols in Cranelifttests. List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

073aedab - Enable the `unsafe-op-in-unsafe-fn` lint (#10559)

Wed, 09 Apr 2025 21:06:59 +0000

Enable the `unsafe-op-in-unsafe-fn` lint (#10559)* Enable the `unsafe-op-in-unsafe-fn` lintThis commit enables the `unsafe-op-in-unsafe-fn` lint in rustc for theentire workspace. This lint will be warn-by-default in the 2024 editionso this is intended to smooth the future migration to the new edition.Many `unsafe` blocks were added in places the lint warned about, withtwo major exceptions. The `wasmtime` and `wasmtime-c-api` crates simplyexpect this lint to fire and effectively disable the lint. They're toobig at this time to do through this PR. My hope is that one day in thefuture they'll be migrated, but more realistically that probably won'thappen so these crates just won't benefit from this lint.* Fix nostd fiber buildprtest:full* Fix build on Windows* Fix asan build List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

48f4621f - Run the full test suite on 32-bit platforms (#9837)

Wed, 15 Jan 2025 18:43:18 +0000

Run the full test suite on 32-bit platforms (#9837)* Run the full test suite on 32-bit platformsThis commit switches to running the full test suite in its entirety(`./ci/run-tests.sh`) on 32-bit platforms in CI in addition to 64-bitplatforms. This notably adds i686 and armv7 as architectures that aretested in CI.Lots of little fixes here and there were applied to a number of tests.Many tests just don't run on 32-bit platforms or a platform withoutCranelift support, and they've been annotated as such where necessary.Other tests were adjusted to run on all platforms a few minor bug fixesare here as well.prtest:full* Fix clippy warning* Get wasm code working by default on 32-bitDon't require the `pulley` feature opt-in on 32-bit platforms to getwasm code running.* Fix dead code warning* Fix build on armv7* Fix test assertion on armv7* Review comments* Update how tests are skipped* Change how Pulley is defaultedDefault to pulley in `build.rs` rather than in `Cargo.toml` to make iteasier to write down the condition and comment what's happening. Thismeans that the `pulley-interpreter` crate and pulley support inCranelift is always compiled in now and cannot be removed. This shouldhopefully be ok though as the `pulley-interpreter` crate is stillconditionally used (meaning it can get GC'd) and the code-size ofCranelift is not as important as the runtime itself.* pulley: Save/restore callee-save state on traps* Fewer clippy warnings about casts* Use wrapping_add in `g32_addr`, fixing arm test List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

0fff9c10 - Enable `missing-unsafe-on-extern` lint (#9963)

Thu, 09 Jan 2025 20:21:25 +0000

Enable `missing-unsafe-on-extern` lint (#9963)* Enable `missing-unsafe-on-extern` lintThis'll be a hard error in the 2024 edition so go ahead and opt-in to itnow to ease our future transition.* Fix adapter build* Fix custom c-api build* Fix fuzzer build* Fix some Windows `extern` blocks List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

fc9ec7a9 - pulley: Support `runtests` in Cranelift filetests (#9795)

Wed, 11 Dec 2024 23:09:28 +0000

pulley: Support `runtests` in Cranelift filetests (#9795)This'll help when adding unit tests for Pulley and/or might be usefulwhen debugging various lowerings and such in the future. I hope toenable more tests in the future once more pulley lowerings areavailable. List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs

71cb94be - Burn down the `allow_attributes_without_reason` backlog (#9712)

Tue, 03 Dec 2024 16:57:45 +0000

Burn down the `allow_attributes_without_reason` backlog (#9712)* Burn down the `allow_attributes_without_reason` backlogJust a bit, not everything fixed.* Fix wasi-nn annotations* Tweak `#[cfg]` List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.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/cranelift/filetests/src/function_runner.rs

17146ab2 - Remove some more cranelift-filetest wasm testing bits (#8143)

Fri, 15 Mar 2024 16:51:17 +0000

Remove some more cranelift-filetest wasm testing bits (#8143)* Delete now-dead code from the wasm runner in cranelift-filetestNo longer needed with tests having moved out to `tests/disas`* Move wasm<->clif testing to `tests/disas.rs`No need for `test_wasm.rs` to stick around in cranelift-filetest, somove the bits up a layer.* Remove wasm crate dependencies* Change bless env var name* Force link to `libm` List of files: /wasmtime-44.0.1/cranelift/filetests/src/function_runner.rs