Changes in static_.rs

557cc2d6 - Another batch of dependency updates (#11832)

Fri, 10 Oct 2025 17:12:23 +0000

Another batch of dependency updates (#11832)* Another batch of dependency updatesBringing some deps in `Cargo.toml` up-to-date with their latest versionsalong the same lines as #11820 to avoid deps getting too stale/old.Code-wise this updates `anyhow` which enables preexisting Clippywarnings to check more code, so those warnings are fixed here as well.prtest:full* Run rustfmt List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/memory/static_.rs

046a51ca - Avoid cloning and dropping `Arc`s in `LocalMemory::vmmemory` (#11148)

Fri, 27 Jun 2025 18:51:03 +0000

Avoid cloning and dropping `Arc`s in `LocalMemory::vmmemory` (#11148)* Avoid cloning and dropping `Arc`s in `LocalMemory::vmmemory`Getting the base pointer from the underlying `dyn RuntimeLinearMemory` involvedgetting a `MemoryBase` which is potentially an `MmapOffset` which itselfcontains an `Arc`, and we would then call `base.as_non_null()` to turnthis into a raw pointer, and then we would drop the `MemoryBase` whichultimately drops the `Arc`. So that's an `Arc` clone and drop just to geta `VMMemoryDefinition`, which is just a pointer and a length, essentially aslice of the linear memory. And, among other places, we call`LocalMemory::vmmemory` to get the GC heap's memory base and bound every time weaccess a GC object from Rust (for example, during collections).Altogether, this removes another 30% of runtime from the testcase inhttps://github.com/bytecodealliance/wasmtime/issues/11141* Construct `VMMemoryDefinition`s in the `RuntimeLinearMemory` implementationInstead of in `LocalMemory` via calling various `RuntimeLinearMemory` methods,as `LocalMemory` has a `dyn RuntimeLinearMemory` object so those calls are allindirect. List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/memory/static_.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/crates/wasmtime/src/runtime/vm/memory/static_.rs

d5ee2a04 - Move MemoryImageSource::map_at to mmap module (#9687)

Fri, 06 Dec 2024 23:51:06 +0000

Move MemoryImageSource::map_at to mmap module (#9687)* Simplify mmap interface slightlyReturn a single `SendSyncPtr` -- the platform-independent context converts tothe various raw pointer types as desired. This simplifies upcoming work where Iwanted to return a `SendSyncPtr`.* Move MemoryImageSource::map_at to mmap moduleThis is part of the work to centralize memory management into the `mmap`module. This commit introduces a few structures which aid in that process, andstarts converting one of the functions (`MemoryImageSource::map_at`) into thismodule.The structures introduced are:* `MemoryBase`: `RuntimeLinearMemory::base_ptr` is now `RuntimeLinearMemory::base`, which returns a `MemoryBase`. This is either a raw pointer or an `MmapOffset` as described below.* `MmapOffset`: A combination of a reference to an mmap and an offset into it. Logically represents a pointer into a mapped section of memory.In future work, we'll move more image-mapping code over to `Mmap` instances. List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/memory/static_.rs

d3132c9d - Add a `signals-based-traps` Cargo compile-time feature (#9614)

Tue, 19 Nov 2024 19:21:36 +0000

Add a `signals-based-traps` Cargo compile-time feature (#9614)* Gate signal handlers behind a new Cargo featureThis commit adds a new on-by-default Cargo feature to the `wasmtime`crate named `signals-based-traps`. This is modeled after the`Config::signals_based_traps` configuration at runtime and can be usedto statically disable the use of signal handlers in Wasmtime. Thisnotably reduces the number of platform dependencies that Wasmtime hasand provides a mode of avoiding relying on signals altogether.This introduces a new `MallocMemory` which is a linear memory backed bythe system allocator. This new type of memory is enabled when virtualmemory guards are disabled and signals-based-traps are disabled. Thismeans that this new type of memory will be candidate for fuzzing forexample.prtest:full* Fix rebase conflict* Refactor `MmapVec` documentation and representation* Remove no-longer-needed `Arc`* Document it may be backed by `Vec` List of files: /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/memory/static_.rs