en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/disas/dead-code.wat#7e0331c2 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/dead-code.wat Wed, 11 Feb 2026 23:43:29 +0000 Chris Fallin <chris@cfallin.org> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/disas/dead-code.wat#10138516 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/dead-code.wat Thu, 05 Dec 2024 17:39:47 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/disas/dead-code.wat#4896b663 Fix tail calls being turned on by default (#8682)* Fix tail calls being turned on by defaultLogic in `Config` to conditionally enable tail calls wasn't handling thecase where the configured compiler strategy was `Strategy::Auto` meaningthat by default tail calls weren't actually enabled. This commitrefactors handling of `Strategy` to avoid storing `Strategy::Auto` in`CompilerConfig` so tests against it can use either cranelift or winch.* Update disas tests* Update Winch tests to using winch List of files: /wasmtime-44.0.1/tests/disas/dead-code.wat Wed, 22 May 2024 21:23:39 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/disas/dead-code.wat#138148a5 Resolve value aliases in disas tests (#8239)This reverts commit 6c5184809db3a92de4ee0c718c403bedc9a9ff4f,"Cranelift: resolve value aliases when printing CLIF functions (#8214)",then applies the same effect a different way.In discussion on #8223, we decided to handle this a different way. SoI've introduced a method on DataFlowGraph which eliminates all valuealiases, and we can call it when necessary. If that function is notcalled then the CLIF printer should print value aliases the same way itdid before #8214.In this PR, I've specifically called it in disas tests. The changes towrite.rs and frontend.rs are from the revert, while the changes todisas.rs are new.In these tests, value aliases are just clutter that distracts fromunderstanding what code will actually be generated. They may change dueto changes in legalization, but that doesn't signal anything aboutwhatever the test was intended to check.Because the new helper deletes aliases after it's done resolving them,those aliases now disappear from the test expectations. Aside from that,the test expectations are unchanged compared to what #8214 did. List of files: /wasmtime-44.0.1/tests/disas/dead-code.wat Tue, 26 Mar 2024 06:36:54 +0000 Jamey Sharp <jsharp@fastly.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/disas/dead-code.wat#6c518480 Cranelift: resolve value aliases when printing CLIF functions (#8214)This makes the CLIF much easier to follow. List of files: /wasmtime-44.0.1/tests/disas/dead-code.wat Fri, 22 Mar 2024 01:24:49 +0000 Nick Fitzgerald <fitzgen@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/disas/dead-code.wat#ead7f735 Compile out wmemcheck-related libcalls when not enabled (#8203)Currently even when the `wmemcheck` Cargo feature is disabled thevarious related libcalls are still compiled into `wasmtime-runtime`.Additionally their signatures are translated when lowering functions,although the signatures are never used. This commit adds `#[cfg]`annotations to compile these all out when they're not enabled.Applying this change, however, uncovered a subtle bug in our libcalls.Libcalls are numbered in-order as-listed in the macro ignoring `#[cfg]`,but they're assigned a runtime slot in a `VMBuiltinFunctionsArray`structure which does respect `#[cfg]`. This meant, for example, that if`gc` was enabled and `wmemcheck` was disabled, as is the default for ourtests, then there was a hole in the numbering where libcall numbers weremismatched at runtime and compile time.To fix this I've first added a const assertion that the runtime-numberof libcalls equals the build-time number of libcalls. I then updated themacro a bit to plumb the `#[cfg]` differently and now libcalls areunconditionally defined regardless of cfgs but the implementation is`std::process::abort()` if it's compiled out.This ended up having a large-ish impact on the `disas` test suite. Lotsof functions have fewer signatures translation because wmemcheck, evenwhen disabled, was translating a few signatures. This also had someassembly changes, too, because I believe functions are considered leavesbased on whether they declare a signature or not, so declaring an unusedsignature was preventing all wasm functions from being considered leaves. List of files: /wasmtime-44.0.1/tests/disas/dead-code.wat Thu, 21 Mar 2024 16:49:11 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/disas/dead-code.wat#27153d07 Move all tests out of `cranelift-wasm` (#8147)* Move remaining `*.wat` tests out of cranelift-wasm/wasmtestsMove these up to Wasmtime's misc testsuite to get translated andinstantiated by Wasmtime.Note that the max-function-index-in-name-section test was removed hereas that's tested by the support added in #3509.* Remove cranelift-wasm test for name sectionThis is pretty thoroughly tested elsewhere in Wasmtime that we respectthe name section, for example many of the trap tests assert that thename of the function comes from the text format.* Move reachability tests out of cranelift-wasmInstead add them to the disassembly test suite to ensure we don'tgenerate dead code. Additionally this has a lot of coverage via fuzzingtoo.* Move more tests out of cranelift-wasmMove them into `tests/disas` so we can easily see the CLIF. List of files: /wasmtime-44.0.1/tests/disas/dead-code.wat Fri, 15 Mar 2024 23:40:23 +0000 Alex Crichton <alex@alexcrichton.com>