Changes in ref-test-array.wat

7e0331c2 - Debugging: refactor stack frame cursor into frame handle abstraction. (#12566)

Wed, 11 Feb 2026 23:43:29 +0000

Debugging: refactor stack frame cursor into frame handle abstraction. (#12566)* Debugging: refactor stack frame cursor into frame handle abstraction.This addresses some of the issues described #12486: we need the abilityto keep a handle to a stack frame as long as execution is frozen, andkeep multiple of these handles around, alongside the `Store`, withoutany handle directly holding a borrow of the store.The frame handles work by means of an "execution version" scheme: theidea is that whenever any execution resumes in a given store, allhandles to existing frames could be invalidated, but if no suchexecution occurs, all handles should still be valid. A tuple of(globally unique for process lifetime) store ID, and execution versionwithin that store, should be sufficient to uniquely identify anyfrozen-stack period during execution. This accomplishes cheap handleinvalidation without the need to track existing handles.This PR also implements a cache of parsed frame-table data. Previouslythis was lazily parsed by the cursor as it walked up a stack, but withmultiple handles hanging around, and with handles meant to be cheap tohold and clone, and with handles being invalidated eagerly, it makesmuch more sense to persist this parsed metadata at the `Store` level.(It cannot persist at the `Engine` level because PCs are local perstore.)* Re-bless disas tests (offsets in VMStoreContext changed).* Handle invalidation tests.* Review comments, and make API return `Result`s rather than panic'ing on stale handles.* Review feedback.* Doc-comment link fix.* Review feedback.* cfg-gate Activation method to `debug` feature only.* Fix unused-import warning in no-debug cfg.* Fix doc link (again, after rename from latest feedback). List of files: /wasmtime-44.0.1/tests/disas/gc/drc/ref-test-array.wat

a80dd80d - Cranelift: Rewrite conditional branches to unconditional traps into conditional traps during legalization (#10988)

Mon, 09 Jun 2025 20:17:02 +0000

Cranelift: Rewrite conditional branches to unconditional traps into conditional traps during legalization (#10988)* Cranelift: Legalize via a backwards walk, rather than forwardsNote: the test expectation change in `filetests/egraph/misc.clif` is simplybecause we happen to change the order in which we created the legalized`stack_addr` instructions that get GVN'd together, and therefore also changedtheir relative value numbering. We dedupe to the value that occurs first in thefunction, which is the one inserted into the DFG *after* the other now becauseof the backwards traversal, and it therefore has a different value number frombefore. The resulting program is identical, modulo value numbering.* Cranelift: Rewrite conditional branches to unconditional traps into conditional traps during legalizationGiven this instruction:```clifbrif v0, block1, block2```If we know that `block1` does nothing but immediately trap then we can rewritethat `brif` into the following:```cliftrapz v0, jump block2```(And we can do the equivalent with `trapz` if `block2` immediately traps).This transformation allows for the conditional trap instructions to be GVN'd andfor our egraphs mid-end to generally better optimize the program. Weadditionally have better codegen in our backends for `trapz` than branches tounconditional traps.Fixes https://github.com/bytecodealliance/wasmtime/issues/10941* Update CLIF filetests and Wasmtime disas tests List of files: /wasmtime-44.0.1/tests/disas/gc/drc/ref-test-array.wat

c22b3cb9 - Reuse Wasm linear memories code for GC heaps (#10503)

Fri, 11 Apr 2025 21:15:55 +0000

Reuse Wasm linear memories code for GC heaps (#10503)* Reuse code for Wasm linear memories for GC heapsInstead of bespoke code paths and structures for Wasm GC, this commit makes itso that we now reuse VM structures like `VMMemoryDefinition` and bounds-checkinglogic. Notably, we also reuse all the associated bounds-checking optimizationsand, when possible, virtual-memory techniques to completely elide them.Furthermore, this commit adds support for growing GC heaps, reusing themachinery for growing memories, and makes it so that GC heaps always start outempty. This allows us to properly delay allocating the GC heap's storage until aGC object is actually allocated.Fixes #9350* fix c api compilation* use assert_contains* remove no-longer-necessary extra memory config from limiter tests* Helper for retry-after-maybe-async-gc in libcalls* Clean up some comments* fix wasmtime-fuzzing and no-gc compilation* fix examples* fix no-gc+compiler build* fix build without pooling allocator* fix +cranelift +gc-drc -gc-null builds* fix table hash key stability test* fix oracle usage of `ExternRef::new`* fix +gc -gc-null -gc-drc build* fix wasmtime-fuzzing* make `StorePtr` wrap a `NonNull`* Fix some doc tests* Remove some unnecessary retry helpers now that `FooRef::new` will auto-gc* fix things after rebase* Reorganize collection/growth methods for GC heap* rename BoundsCheck variants* fix cfg'ing of gc only code* Fix doc tests* fix one more gc cfg* disable GC heap OOM test on non-64-bit targets List of files: /wasmtime-44.0.1/tests/disas/gc/drc/ref-test-array.wat

4d876371 - Add "pure" flag to `ir::MemFlags` (#10340)

Thu, 06 Mar 2025 21:51:49 +0000

Add "pure" flag to `ir::MemFlags` (#10340)* Add "pure" flag to `ir::MemFlags`This flag represents whether the memory operation's safety (e.g. the validity ofits `notrap` and `readonly` claims) is purely a function of its datadependencies.If this flag is `true`, then it is okay to code motion this instruction toarbitrary locations, in the function, including across blocks and conditionalbranches, so long as data dependencies (and trap ordering, if relevant) areupheld.If this flag is `false`, then the memory operation's safety potentially reliesupon invariants that are not reflected in its data dependencies, and thereforeit is not safe to code motion this operation. For example, this operation couldbe in a block that is dominated by a control-flow bounds check that makes thisoperation safe, and that invariant is not reflected in its operands. It would beunsafe to code motion such an instruction above its associated bounds check,even if its data dependencies would still be satisfied.I've added this flag because we were doing exactly that kind of code motionwhere we moved a `readonly` and `notrap` memory operation past its associatednull-check and therefore it was no longer safe to perform and we would get asegfault. This could only be triggered when the Wasm typed-function-referencesproposal was enabled, which is not a tier-1 proposal, so it is not considered avulnerability. Nonetheless, it is a pretty scary kind of bug, and other codepaths weren't affected due to pretty subtle interactions. And this is themotivation for the new "pure" flag: without needing to explicitly opt intodata-dependency-based code motion (i.e. set the "pure" flag), it is too easy toaccidentally move loads past their control-flow-based safety guards.* fix load-hoisting test; also test that non-pure loads don't hoist* Rename `pure` flag to `can_move` List of files: /wasmtime-44.0.1/tests/disas/gc/drc/ref-test-array.wat

2f56a321 - Slightly simplify logic in `ref.test` translation (#10192)

Thu, 06 Feb 2025 06:59:47 +0000

Slightly simplify logic in `ref.test` translation (#10192)When the ref is null or i31, just use an `iconst` result value directly, ratherthan reusing the result of the check for null or i31. Reusing the result doesn'tactually yield better code (equivalently good or worse depending on if null/i31are allowed or not) and is somewhat subtle -- I have to stop and re-thinkthrough its correctness each time I see it again -- so this change should be awelcome improvement.This does not change the logic of the emitted code, but does slightly change theemitted code itself. List of files: /wasmtime-44.0.1/tests/disas/gc/drc/ref-test-array.wat

10138516 - Shuffle fields in `VMRuntimeLimits` (#9739)

Thu, 05 Dec 2024 17:39:47 +0000

Shuffle fields in `VMRuntimeLimits` (#9739)* Shuffle fields in `VMRuntimeLimits`Right now this structure has a pointer-sized field, two 64-bit integers,and then three pointer-sized fields. This structure's layout isnontrivial to calculate on 32-bit platforms as it needs to take thealignment of 64-bit integers into account which differs between ARM andx86 for example. To make this easier shuffle all the 64-bit integers are nowfirst, which means we don't have to worry about alignment.I'll note that this particular ordering is still a bit brittle becausewe might need to shuffle things again if more fields are added. Thatbeing said any misalignment is caught during testing of the `wasmtime`crate so there's not much danger in adding more things, it'll justrequire updating a few more locations.* Update test expectations List of files: /wasmtime-44.0.1/tests/disas/gc/drc/ref-test-array.wat

83bf774d - Add the "null" garbage collector (#9484)

Thu, 31 Oct 2024 17:46:17 +0000

Add the "null" garbage collector (#9484)* Add the "null" garbage collectorThe null collector does not actually collect any garbage, it simplybump-allocates until the heap is exhausted, at which point further allocationattempts will fail. It does not require any GC barriers.Users can configure which collector to use via the `wasmtime::Config::collector`method or the `-C collector=drc|null` CLI flag. The `wasmtime::Collector` enumeration,similar to the `wasmtime::Strategy` enumeration but for choosing a collectorrather than a compiler, additionally has a table summarizing the properties andcharacteristics of our current set of collector implementations.Finally, we also run `.wast` tests that exercise GC types under both the DRC andnull collectors. I tried to avoid running tests that are not related to GC underboth configurations just to avoid a combinatorial blow up.* cargo fmt* fix +gc -gc-null -gc-drc build* Fix some warnings in various cargo feature combo builds* Fix some more warnings in certain build configs* Fix unit tests for null GC* Fill in some placeholder comments that I forgot to write* Fix issues where we ask for a GC store when we don't actually need oneWhich was causing test failures, since we no longer return a GC store with adummy heap.* Add fuzzing config support for different collectors* address review feedback* fix cmake tests* Fix test compilation after rebase* Fix GC tests under MIRI List of files: /wasmtime-44.0.1/tests/disas/gc/drc/ref-test-array.wat