Changes in debug_builtins.rs

900370bc - Make core wasm libcalls sound (#11496)

Thu, 21 Aug 2025 22:05:11 +0000

Make core wasm libcalls sound (#11496)* Make core wasm libcalls soundThis commit updates the signature of core wasm libcalls to look morelike component libcalls where the instance argument is just an id, notan actual pointer. This is required to make them sound because otherwiseit's possible to, in safe Rust, acquire two mutable pointers to the sameinstance. Implementing this change is made possible by the many manyprevious refactors to how all of these internals work. All that wasrequired here was changing type signatures and minor updates to theorder of operations inside of libcalls.Closes #11178* Fix wmemcheck build List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

82941262 - Require a store in `catch_unwind_and_record_trap` (#11441)

Mon, 18 Aug 2025 20:11:15 +0000

Require a store in `catch_unwind_and_record_trap` (#11441)* Require a store in `catch_unwind_and_record_trap`This commit does some preparatory refactoring for #11326 to ensure thata store is available when trap information is being processed. Currentlythis doesn't leverage the new parameter but it should be leverage-ablein #11326.* Review comments List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

74efac71 - Allow compiling debug-builtins in no_std environment to enable gdb jit (#11304)

Tue, 29 Jul 2025 20:20:31 +0000

Allow compiling debug-builtins in no_std environment to enable gdb jit (#11304)* Allow compiling debug-builtins in no_std environment to enable gdb jit- Make jit-debug crate #![no_std] when `std` feature is not enabled- Make gdb_jit_int module build in no_std environment- Use std when perf_jitdebug is enabled because the perf_jitdebug module does not run in no_std environment- Change debug-builtins feature to only enable gdb_jit_int- The perf_jitdebug feature is enabled in profiling mode onlySigned-off-by: Doru Blânzeanu * Remove feature listing from `default`These are otherwise present via `std`.* Shuffle around some features* Enable `wasmtime-jit-debug/std` from wasmtime's `std` feature* Only enable `perf_jitdump` from `profiling` as that's all that's explicitly needed.* Remove empty features list* Cut down on some `#[cfg]` usage* Update comments in gdb_jit_int module* Add CI checks that `debug-builtins` builds on no_std* Fix missing has_host_compiler_backend when debug-builtins enabledSigned-off-by: Doru Blânzeanu ---------Signed-off-by: Doru Blânzeanu Co-authored-by: Alex Crichton List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

35786823 - Deny `unsafe_op_in_unsafe_fn` in `wasmtime::runtime::vm` (#11312)

Wed, 23 Jul 2025 21:50:06 +0000

Deny `unsafe_op_in_unsafe_fn` in `wasmtime::runtime::vm` (#11312)* Deny `unsafe_op_in_unsafe_fn` in `wasmtime::runtime::vm`Slowly expanding this lint to more of the crate.prtest:full* Fix lints in custom module* Fix some lints with miri* Fix non-VM build* Fix arm windows List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

f021346e - More table safety improvements (#11255)

Thu, 17 Jul 2025 17:15:13 +0000

More table safety improvements (#11255)* More table safety improvementsThis is some more progress on #11179 aimed at improving the safety ofmanagement of tables internally within Wasmtime:* `Instance::table_index` is removed as it can be replaced with data stored directly in the `VMTableImport` now.* `Instance::get_table` now returns `&mut Table`* `Instance::get_defined_table_with_lazy_init` now returns `&mut Table`* `Instance::with_defined_table_index_and_instance` now directly returns `DefinedTableIndex` plus `Pin<&mut Instance>`, codifying the ability to "laterally move" between instances.* `Instance::table_init_segment` was refactored to "take" the tables during initialization and replace them afterwards, resolving the split borrow issue and removing an `unsafe` block in the function.cc #11179* Improve safety of `Table::copy`This commit fixes an issue in the previous commit with respect to Miriand Stacked Borrows. This does so by improving the safety of the`Table::copy`-related functions to all work mostly on safe code ratherthan unsafe references. Some minor amount of unsafety is still presentbut it is now clearly documented and easier to verify.* Fix tests List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

e16780de - fix typos in Runtime VM Source Files (#11158)

Mon, 30 Jun 2025 14:57:34 +0000

fix typos in Runtime VM Source Files (#11158)* Update debug_builtins.rs* Update libcalls.rs* Update stack_switching.rs List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

b86b9682 - Provenance preparation for Pulley (#10043)

Thu, 23 Jan 2025 20:55:28 +0000

Provenance preparation for Pulley (#10043)* Provenance preparation for PulleyThis commit is an internal refactoring of Wasmtime's runtime to prepareto execute Pulley in MIRI. Currently today this is not possible becausePulley does not properly respect either strict or permissive provenancemodels. The goal of this refactoring is to enable fixing this in afuture commit that doesn't touch everything in the codebase. Insteadeverything is touched here in this commit.The basic problem with Pulley is that it is incompatible with the strictprovenance model of Rust which means that we'll be using "exposedprovenance" APIs to satisfy Rust's soundness requirements. In this modelwe must explicitly call `ptr.expose_provenance()` on any pointerswhich are exposed to compiled code. Arguably we should also be alreadydoing this for natively-compiled code but I am not certain about howstrictly this is required.Currently in Wasmtime today we call `ptr.expose_provenance()` nowhere.It also turns out, though, that we share quite a few pointers in quite afew places with compiled code. This creates a bit of a problem! Thesolution settled on in this commit looks like:* A new marker trait, `VmSafe`, is introduced. This trait is used to represent "safe to share with compiled code" types and enumerates some properties such as defined ABIs, primitives wrappers match primitive ABIs, and notably "does not contain a pointer".* A new type, `VmPtr`, is added to represent pointers shared with compiled code. Internally for now this is just `SendSyncPtr` but in the future it will be `usize`. By using `SendSyncPtr` it shouldn't actually really change anything today other than requiring a lot of refactoring to get the types to line up.* The core `vmctx_plus_offset*` methods are updated to require `T: VmSafe`. Previously they allowed any `T` which is relatively dangerous to store any possible Rust type in Cranelift-accessible areas.These three fundamental changes were introduced in this commit. Allfurther changes were refactoring necessary to get everything workingafter these changes. For example many types in `vmcontext.rs`, such as`VMFuncRef`, have changed to using `VmPtr` instead of `NonNull` or`*mut T`. This is a pretty expansive change which resulted in touching alot of places.One premise of `VmPtr` is that it's non-null. This was anadditional refactoring that updated a lot of places where previously`*mut T` was used and now either `VmPtr` or `NonNull` is used.In the end the intention is that `VmPtr` is used whenever pointersare store in memory that can be accessed from Cranelift. When operatinginside of the runtime `NonNull` or `SendSyncPtr` is preferredinstead.As a final note, no provenance changes have actually happened yet. Forexample this doesn't fix Pulley in MIRI. What it does enable, though, isthat the future commit to fix Pulley in MIRI will be much smaller withthis having already landed.* Run the full test suite in PR CIprtest:full* Minor CI issues* Fix no_std build* Fix miri build* Don't use `VmPtr` in FFI function signaturesUse `NonNull` or `*mut u8` as appropriate for function signaturesinstead. It shouldn't be required to use `VmPtr` during the handoff tocompiled code as we've already annotated the pointer going out.* Fix rebase conflict* Review comments List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.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/crates/wasmtime/src/runtime/vm/debug_builtins.rs

115da98d - Move gdbjit C helpers to a separate file (#9939)

Tue, 07 Jan 2025 15:56:22 +0000

Move gdbjit C helpers to a separate file (#9939)* Move gdbjit C helpers to a separate fileThis commit splits out the gdbjit-related helpers from `helpers.c` inWasmtime to a separate C file built as part of the `wasmtime-jit-debug`crate. This'll help excise these helpers if gdbjit support is disabledat compile time and additionally brings them closer to the actualdefinition in the `wasmtime-jit-debug` crate.* Fix linkage issues* Fix miri tests List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

8e4f0cd3 - Export debug builtins on Windows (#9706)

Mon, 02 Dec 2024 20:31:32 +0000

Export debug builtins on Windows (#9706)This allows the debugger to find them.After much research, this has been chosen as the overall best solution.The alternative here would be to create machine code thunks that callthese symbols when Jitting code, and describing those thunks in DWARF,which would be significantly more complex. List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

2a7f0653 - Remove the `wasmtime_environ::MemoryPlan` type (#9532)

Thu, 31 Oct 2024 20:46:03 +0000

Remove the `wasmtime_environ::MemoryPlan` type (#9532)* Remove the `wasmtime_environ::MemoryPlan` typeThis is the equivalent of #9530 for memories. The goal of this commit isto eventually remove the abstraction layer of `MemoryPlan` and`MemoryStyle` in favor of directly reading the configuration of`Tunables`. The prediction is that it will be simpler to work directlywith configured values instead of a layer of abstraction between theconfiguration and the runtime which needs to be evolved independently tocapture how to interpret the configuration.Like with #9530 my plan is to eventually remove the `MemoryStyle` typeitself, but that'll be a larger change, so it's deferred to a futurePR.* Fix shared memory disabled build List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

2bdae8b6 - Rename the `wasmtime::runtime::vm::Instance::module` method to `env_module` (#9261)

Mon, 16 Sep 2024 22:28:46 +0000

Rename the `wasmtime::runtime::vm::Instance::module` method to `env_module` (#9261)Because it returns the `wasmtime_environ::Module`.This paves the way for a new method to get the `wasmtime::Module`. List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs

72004aad - Turn the `wasmtime-runtime` crate into the `wasmtime::runtime::vm` module (#8501)

Tue, 30 Apr 2024 18:52:45 +0000

Turn the `wasmtime-runtime` crate into the `wasmtime::runtime::vm` module (#8501)* Expose `wasmtime-runtime` as `crate::runtime::vm` internally for the `wasmtime` crate* Rewrite uses of `wasmtime_runtime` to `crate::runtime::vm`* Remove dep on `wasmtime-runtime` from `wasmtime-cli`* Move the `wasmtime-runtime` crate into the `wasmtime::runtime::vm` module* Update labeler for merged crates* Fix `publish verify`prtest:full List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/debug_builtins.rs