Changes in module.rs

1b59b579 - Add support for map type (#12216)

Mon, 09 Mar 2026 23:34:21 +0000

Add support for map type (#12216)* Add support for map typeSigned-off-by: Yordis Prieto * Add Map and MapEntry classes to support key/value pairs in component modelThis commit introduces the Map and MapEntry classes, enabling the representation of map values in the component model. The Map class allows for the creation and iteration of key/value pairs, enhancing the functionality of the wasmtime component API. Additionally, the .gitignore file is updated to exclude build artifacts from the crates/c-api directory.* Add wasm_component_model_map configuration support* Format code* Format C code* Enhance component model to support HashMap typeThis commit introduces support for HashMap in the component model, allowing maps to be represented as list> in the canonical ABI. It includes implementations for the ComponentType, Lower, and Lift traits for HashMap, enabling type checking, lowering to flat representations, and lifting from memory. Additionally, the maximum depth for type generation in the fuzzing utility is updated to accommodate the new map type.* Refactor component configuration to introduce map supportThis commit removes the previous wasm features configuration and adds new functions for creating a map-configured engine. The `map_config` and `map_engine` functions are introduced to facilitate the use of the component model with maps in tests, ensuring that the engine is properly configured for map types in the component model.* Add new WAST test for map types and remove map type definitions from existing testsThis commit introduces a new WAST test file specifically for testing various map types in the component model. Additionally, it removes the redundant map type definitions from the existing types.wast file to streamline the test suite.* Update component fuzzing and dynamic tests to replace call_and_post_return with call* Format code* Refactor HashMap usage in typed.rs to use wasmtime_environ collections* Fix HashMap initialization and insertion to handle potential errors in typed.rs* Refactor HashMap handling in typed.rs to use lower_map_iter for improved iteration and memory management. Introduce new implementations for ComponentType, Lower, and Lift traits for std::collections::HashMap, enhancing support for map types in the component model.* Fix map adapter trampoline compilation and alignment bugsThe translate_map function had two categories of bugs preventing mapadapter trampolines from working:1. Wasm stack discipline: local_set_new_tmp emits LocalSet which pops from the stack, but was called when the stack was empty (to "pre-allocate" locals). Fixed by computing values first, then calling local_set_new_tmp to consume them—matching translate_list's pattern. Also removed an erroneous LocalTee that left an orphan value on the stack. Affected: src_byte_len, dst_byte_len, cur_src_ptr, cur_dst_ptr.2. Pointer advancement: after value translation, the pointer still points at the value start. The code only advanced by trailing padding instead of value_size + trailing_padding, causing every loop iteration to re-read the same memory.Also fixes entry layout to use proper record alignment rules (entryalign = max(key_align, value_align), value at aligned offset).* Refactor map entry layout calculations to use canonical ABI* Remove unnecessary clone of map pairs during loweringVal::Map already holds Vec<(Val, Val)> which derefs to &[(Val, Val)],matching lower_map's signature directly. The intermediate Vec allocationand deep clone of every key/value pair was redundant.* Deduplicate map lift logic between HashMap implementations* Deduplicate list and map sequence translation scaffolding* Fix cargo fmt formatting issues* Deduplicate map typecheck logic* Deduplicate map lowering with linear_lower_map_to_flat and linear_lower_map_to_memory helpers* Clean up lift_try_map: use drop, move TryHashMap import to module scope* Fix CI: arbtest overflow and no-std HashMap lift_map- component_fuzz: use saturating_sub in generate_hashable_key to prevent underflow when fuel is 0 and Enum variant is chosen- typed: remove incorrect ? operators in lift_map for hashbrown::HashMap (with_capacity and insert don't return Result)* Store map tuple layout in TypeMapCompute map entry ABI and value offsets once during type building, and reuse that metadata in runtime map lift/lower paths instead of recalculating tuple layout at each call site.* Refactor map ABI argument passingBundle map lift/lower layout and type metadata into a small MapAbi32 helper so map helper calls stay concise without changing behavior.* Fix CI: enable component_model_map in fuzzing and handle map in arbitrary_valThe fuzzer's component_api oracle was generating map types but the enginedidn't have the map feature enabled, and arbitrary_val had no arm forType::Map. Enable component_model_map in the store helper (matching howcomponent_model_async is forced on) and implement arbitrary value generationfor map types.---------Signed-off-by: Yordis Prieto List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

caf0f752 - Minimal implementation of fixed-length lists to enable wit-bindgen runtime tests (#10619)

Wed, 14 Jan 2026 16:12:38 +0000

Minimal implementation of fixed-length lists to enable wit-bindgen runtime tests (#10619)* necessary parts to make the wit-bindgen test pass* post-merge fixes* fix clippy* inline type computations* link missing functionality to an issue* undo unintended removal of blank line* fix logic mistake, enable feature in wasmtime* optimized conversion* add offset* unify on name and implement wast option* cargo fmt and beautify fixed_size_list_type* add multi memory as it is needed by the test runner* standardize on the official name (component model standard) "fixed-length lists"changing wasm-tools (parser etc. is a different task)* More instances of fixed size corrected to fixed length List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

0a55f804 - "Downgrade" threads support to tier 2, disable fuzzing (#12036)

Mon, 24 Nov 2025 17:09:20 +0000

"Downgrade" threads support to tier 2, disable fuzzing (#12036)* "Downgrade" threads support to tier 2, disable fuzzingThis commit is borne out of a fuzz bug that was opened recently. Thefuzz bug specifically has to do with fallout from #12022, specifically`SharedMemory` being used to allocated instead of `Memory`. In thissituation the resource limiter is no longer consulted meaning thatshared memories bypass this and aren't caught by OOM checks. This iscurrently by design because `SharedMemory` instances don't know whichresource limiter to hook into per-store.More generally though the implementation of wasm threads, while workablein Wasmtime, has a number of known relatively large deficiencies. Thesewere not resolved prior to ungating the wasm proposal (that's on me) butnevertheless the quality of implementation is not quite up to "tier 1par" with the rest of what Wasmtime offers. Given this the threadsproposal is now downgraded to tier 2. To help minimize the impact ofthis the wasm proposal is left enabled-by-default, but creation of a`SharedMemory` in the Rust API requires opting-in via a new`Config::shared_memory` method.This commit shuffles around some documentation of wasm proposals tosplit it into tier 1/2/3 instead of on/off-by-default and then adds acolumn for whether the proposal is on-by-default.* clangformat* Fix tests* Add tests for failed creationFix an issue where defined shared memories weren't gated* Sync disabled threads stub* Fix another testprtest:full* Fix fuzzing tests* Fix dwarf tests List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

e06fbf70 - Cooperative Multithreading (#11751)

Mon, 27 Oct 2025 21:39:35 +0000

Cooperative Multithreading (#11751)* Initial work* Almost compiling* Partially working* Cleanup* Fix merge* Cancellation and suspension refactoring* Remove printlns* Test with several threads* More testing* Cancellation* Fix cancellation for explicit suspends* Finish cancellation test* Store threads in the instance table* Deletion almost there* Tests all pass* Tighten up task deletion* Set thread state correctly* Store pairs of thread and task ids* Remove lift abi members* Cleanup unnecessary change* More cleanup* Cleanup* Revert cargo changes* Revert cargo changes* Comments* Comments on test* Update comments* Update comments* Add space that was removed in an earlier commit* Cleanup* Delete threads from the instance table* Revert cargo file* Remove dead code* Clippy changes* Clippy* Revert unnecessary changes* Revert unnecessary changes* Revert unnecessary changes* Revert unnecessary changes* Revert unnecessary changes* Review comments* Review feedback* Make thread IDs per-component-instance* Fix config* Tighten up completion* Clippy* Trigger full PR test* Move funcref table reading* Remove unused import* Formatting* Rename RemoveOnDrop* Review feedback* Review feedback* Move start thread closure* Review feedback* Review feedback* Correct feature for import* Review feedback* Disable failing tests* Enable fixed tests* Review feedback* Readd tests* Ignore task deletion test with Miri List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

3aa39239 - Exceptions: add basic support for fuzzing. (#11511)

Fri, 22 Aug 2025 17:24:40 +0000

Exceptions: add basic support for fuzzing. (#11511)* Enable use of exceptions in our fuzz module generator.This patch was provided by Alex in #11505; it is thusCo-authored-by: Alex Crichton * Add ExnRef comparison to differential result checking.---------Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

8801023b - Initial component model and GC support in fused adapters (#11020)

Wed, 18 Jun 2025 20:36:26 +0000

Initial component model and GC support in fused adapters (#11020)* Initial component model and GC support in fused adaptersThis lays down the initial infrastructure for support for GC in our fusedadapters for the component model. We keep track of whether each lifted/loweredfunction wants args/results as GC values or in linear memory. We additionallyplumb through the core function types of the functions being lifted and loweredfor (eventual) use with GC adapters.Ultimately, this commit is enough to fuse together lifted and lowered functionswhere one or both are using the GC variant of the canonical ABI. Attempting toactually pass arguments will hit `todo!()`s. The work of implementing those`todo!()`s is left to future commits.* Address review feedback* More review feedback* Fix wasmtime-fuzzing build* Fix the `factc` example program* cargo fmt* Fix fact-valid-module fuzzer List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

c857f687 - Add plumbing for `error-context` component model feature (#10807)

Tue, 27 May 2025 16:35:26 +0000

Add plumbing for `error-context` component model feature (#10807)This commit adds plumbing in locations for the `error-context` featureof the component model. This is porting some minor changes from thewasip3-prototyping repository back to the main repo. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

e6759845 - Log module "DNA" during fuzzing (#10612)

Fri, 18 Apr 2025 17:07:58 +0000

Log module "DNA" during fuzzing (#10612)This commit updates the fuzzing infrastructure of the `wasmtime-fuzzing`crate to record the "DNA string" of a module used to generate a modulein a `*.dna` file. This is accompanied with a `*.json` file to pass to`wasm-tools smith --config`. The end result is that it should bepossible now to more easily reproduce a module generation outside ofWasmtime itself when reproducing bugs and such.Creation of these files is gated on the debug log level in a similarmanner to creation of normal wasm files is gated on the debug log leveltoo. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

366f320d - Update wasm spec test suite, add exception feature flags (#10553)

Tue, 08 Apr 2025 22:00:49 +0000

Update wasm spec test suite, add exception feature flags (#10553)* Update wasm spec test suite, add exception feature flagsThis commit performs an update of the spec test suite submodule to thenext-to-latest commit. The latest commit will require updating the`wast` dependency which isn't published yet.This update brings in the `wasm-3.0` folder of tests since it's beenawhile since the last update. That update notably means that theexception-handling proposal is mixed in with all the others with varioustests. Getting tests as flagged as passing or failing as a result wasunexpectedly difficult.The solution I ended up settling on was to preemptively implement someinfrastructure for the exceptions proposal:* `wasmtime::Config` methods* `wasmtime` CLI flags* integration with wast testing* various updates to `should_fail`It turns out we can run a few tests with the exception proposal, notablydue to tags being implemented for stack switching. That meant that thiscouldn't blanket ignore the exceptions proposal and say it's expected tofail. Instead the proposal is said "this passes!" and tests areindividually listed as "this is expected to fail".This then required changing an `unsupported!` panic to plumbing errorsaround to avoid actually implementing the exceptions proposal here.* Review comments List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

c7e092d8 - Update wasm-tools crates to 1.228.0 (#10501)

Wed, 02 Apr 2025 15:29:19 +0000

Update wasm-tools crates to 1.228.0 (#10501)* Update wasm-tools crates to 1.228.0* Add missing canonical builtins* Add new component model feature flags* Vet wasm-tool dependencies using wildcard* Fix tests hidden behind new CM featuresSeveral CM-async tests were failing due to upstream changes to thecanonical builtins. Here we add some new Wasmtime flags for enablingthese new features, `wasm_component_model_async_builtins` and`wasm_component_model_async_stackful`, and propagate that far enough toenable the features for these tests. This also involved removing all theerror context details from these builtins.Co-authored-by: Alex Crichton * Add some additional plumbing for fuzz configurationprtest:full---------Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

5b9e8765 - Enable the GC proposal during general fuzzing (#10332)

Wed, 12 Mar 2025 18:35:54 +0000

Enable the GC proposal during general fuzzing (#10332)* Enable the GC proposal during general fuzzingThis allows us to fuzz Wasm GC in our fuzz targets that use the commonconfig-generation infrastructure, such as the differential fuzz target.Fixes #10328* Make handling of non-deterministic errors more robust in differential fuzzer* remove logging from functions that can be called from signal handlers List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

1e5d77d6 - chore: fix some typos in comments (#10309)

Fri, 28 Feb 2025 15:53:22 +0000

chore: fix some typos in comments (#10309)Signed-off-by: shenpengfeng List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

287e8fb5 - Update wasm-tools crates to 226 (#10235)

Wed, 19 Feb 2025 20:38:07 +0000

Update wasm-tools crates to 226 (#10235)* Update wasm-tools crates to 226This commit updates the wasm-tools crates to the 226 track of versions.The most notable change here is the removal and refactoring withinwasm-tools of support for multiple and named returns in the componentmodel along with the support for 33+ flags in the `flags` type. This hasbeen gated for some time now and it's just now being removed now thatit's been awhile an no issues have been raised.prtest:full* Fix some issues from CI* Fix benchmarks* Switch to crates.io-based crates List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

3ba13d1b - add component-model-async/lift.wast test (#10083)

Fri, 24 Jan 2025 17:00:54 +0000

add component-model-async/lift.wast test (#10083)This is another piece of #9582 which I'm splitting out to make review easier.This test includes two components: one which exports a function using theasync-with-callback ABI, and another which uses the async-without-callback ABI.It doesn't actually instantiate or run either component yet.The rest of the changes fill in some TODOs to make the test pass.Signed-off-by: Joel Dice List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.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/crates/fuzzing/src/generators/module.rs

3aac2af4 - Update extended-const fuzzing (#9605)

Fri, 15 Nov 2024 05:07:42 +0000

Update extended-const fuzzing (#9605)* Remove the one-off configuration option for this which now duplicates what's in `wasm-smith`.* Reach whether or not the feature is enabled from `wasm-smith`.* Update docs of wasm proposals for some recent changes (e.g. `extended-const` is fuzzed. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

f406347a - Improve fuzzing of `*.wast` tests (#9587)

Mon, 11 Nov 2024 21:00:34 +0000

Improve fuzzing of `*.wast` tests (#9587)* Improve fuzzing of `*.wast` testsCurrently we have a fuzzer which is tasked with running `*.wast` testswith fuzz-generated configurations. This asserts that we at leastsatisfy all basic wasm semantics regardless of how various knobs in`Config` are turned (modulo limits to resources). The current fuzzingthough is not comprehensive in that it doesn't include all the spectests that we pass from all proposals. This runs the risk of we don'tactually fuzz anything until the spec tests are merged upstream, whichcan take a significant amount of time.This commit refactors the `*.wast`-management infrastructure to sharetest discovery and feature calculation between `tests/wast.rs` andfuzzing. This new support crate centralizes limits and discovery forboth to use. Additionally fuzzing is updated to no longer throw out testcases if configuration isn't applicable but instead clamp configurationto the minimum required values (e.g. features + resource limits). Thismeans that we should now be fuzzing all spec tests that pass in allconfigurations.This new fuzzer discovered a few minor issues with the GC proposalimplementation, for example, such as:* Some instructions were translated using trapping methods directly on `FunctionBuilder` rather than `FuncEnvironment` meaning they didn't properly handle `signals-based-traps` configuration.* Fuel handling for `return_call_ref` wasn't correct because it was accidentally omitted from the list of return-call instructions that need special treatment.* Add some manifest metadata List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

84852f72 - Don't use `MemoryStyle` for heap base pointer relocations (#9569)

Wed, 06 Nov 2024 18:10:13 +0000

Don't use `MemoryStyle` for heap base pointer relocations (#9569)* Don't use `MemoryStyle` for heap base pointer relocationsInstead add a helper method to `Memory` which indicates whether the basepointer of memory can move. Use this and plumb the result around to thevarious locations that require it. This improves the `readonly`application of the base pointer in Cranelift by having the optimizationkick in in more scenarios. It additionally fixes combining shared linearmemories with 64-bit addressing or a page size of 1 by adding a runtimecheck before relocation of a linear memory that it's allowed to do so.A few codegen tests are added to ensure that `readonly` is applied whereit wasn't previously and additionally a new `*.wast` test was added withthe cross product of various features of linear memories and some basictests to ensure that the memories all work as expected.This refactoring fixes two preexisting issues about `shared` memoriesrequiring a "static" memory style. The restriction is now based onwhether the pointer can relocate or not and that's upheld via the newtrait method added here.To account for these bug fixes the fuzzers have been updated to allowmixing the `threads` proposal with `memory64` or `custom-page-sizes`.Closes #4267Closes #9523* Optionally increase the allocation size for dynamic memoriesThis code will be short-lived due to scheduled future refactorings butthe idea is that when a "dynamic" memory is chosen the minimum size ofthe allocation needs to be at least `tunables.memory_reservation` to fitthe constraints of the rest of the system, so be sure to factor thatin. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

39391722 - Disable fuzzing both custom-page-sizes and threads (#9524)

Wed, 30 Oct 2024 16:53:48 +0000

Disable fuzzing both custom-page-sizes and threads (#9524)This is an attempt to avoid #9523 in the fuzzers while that issue isfixed independently. Fuzzing is pretty limited right now so the hope isto let fuzzers find other issues while the refactoring here progresses. List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs

edad0bbc - Add general fuzzing support for custom page sizes (#9462)

Wed, 16 Oct 2024 19:04:06 +0000

Add general fuzzing support for custom page sizes (#9462)* Add general fuzzing support for custom page sizes* Add custom-page-sizes as an expected feature for module generation List of files: /wasmtime-44.0.1/crates/fuzzing/src/generators/module.rs