en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#0a55f804 "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/tests/all/memory.rs Mon, 24 Nov 2025 17:09:20 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#698028ce Add a configuration knob for `PAGEMAP_SCAN` (#11433)* Add a configuration knob for `PAGEMAP_SCAN`This commit adds `PoolingAlloationConfig::pagemap_scan` and additionallyadds `-Opooling-pagemap-scan` to configure on the CLI. This is the sametri-state configuration option as `MpkEnable` so that enum was renamedto just `Enabled` and repurposed for both options.This then additionally turns the option off-by-default instead of theprevious on-by-default-if-able-to to enable more slowly rolling out thisfeature.* Fix broken test List of files: /wasmtime-44.0.1/tests/all/memory.rs Thu, 14 Aug 2025 22:07:53 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#df725421 Simplify some conditional testing logic for Winch (#11166)* Simplify some conditional testing logic for WinchRun all tests on all platforms in `#[wasmtime_test]` for Winch without`#[cfg]` and use the result of `should_fail` to determine whether itshould fail or not (e.g. still expect failure on riscv64/s390x/etc).* Ignore non-Pulley tests on Miri List of files: /wasmtime-44.0.1/tests/all/memory.rs Tue, 01 Jul 2025 22:42:30 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#60269d64 winch(aarch64) Run integration tests in winch-aarch64 (#11031)* winch(aarch64) Run integration tests in winch-aarch64This commit closeshttps://github.com/bytecodealliance/wasmtime/issues/8321With https://github.com/bytecodealliance/wasmtime/pull/11013, Winchpasses all spec tests for Core Wasm on Aarch64.* Run `cargo fmt`* Add an `integration` option to `TestConfig``wast::TestConfig` is shared across spec tests and integration tests,this commits adds a flag to identify if the config is for integrationtest purposes making it easier to contextually decide if tests areexpected to fail or pass depending on the Wasm configuration options.* Use `spec_test` instead of `integration`To better differentiate spec tests from integration tests* Ensure only aarch64 / x64 when testing Winch* Revert directive for typed_v128 testPut back `#[wasmtime_test(wasm_features(simd),strategies(not(Winch)))]`; the reason why this tests shouldn't runwith Winch is because it requires AVX, but we can have a generic ruleat the test config level since not all SIMD based tests require AVX,it really depends on which SIMD instructions are used. List of files: /wasmtime-44.0.1/tests/all/memory.rs Mon, 16 Jun 2025 13:36:32 +0000 Saúl Cabrera <saulecabrera@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#90ac295e 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/tests/all/memory.rs Mon, 19 May 2025 16:40:55 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#e657756d Run CI tests through AddressSanitizer (#10537)This is similar to running tests in Valgrind (which we should perhapsalso do...) but can be useful for catching use-after-free style bugsfaster than when a process crashes. Given the unsafe nature of Wasmtimethis is something we should have probably enabled awhile back butotherwise so long as it doesn't take too long to run on CI seems like aneasy win of a boost-of-confidence.prtest:asan List of files: /wasmtime-44.0.1/tests/all/memory.rs Thu, 10 Apr 2025 15:35:08 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#073aedab Enable the `unsafe-op-in-unsafe-fn` lint (#10559)* Enable the `unsafe-op-in-unsafe-fn` lintThis commit enables the `unsafe-op-in-unsafe-fn` lint in rustc for theentire workspace. This lint will be warn-by-default in the 2024 editionso this is intended to smooth the future migration to the new edition.Many `unsafe` blocks were added in places the lint warned about, withtwo major exceptions. The `wasmtime` and `wasmtime-c-api` crates simplyexpect this lint to fire and effectively disable the lint. They're toobig at this time to do through this PR. My hope is that one day in thefuture they'll be migrated, but more realistically that probably won'thappen so these crates just won't benefit from this lint.* Fix nostd fiber buildprtest:full* Fix build on Windows* Fix asan build List of files: /wasmtime-44.0.1/tests/all/memory.rs Wed, 09 Apr 2025 21:06:59 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#d928d8dc s390x: Skip memory allocation failure tests (#10530)These tests assume that a very large allocation will fail due toexceeding address space limits. This is not the case on s390x,where the full 64-bit address space is available for allocation.(Of course, actually using that much memory would still fail atsome point, but the mere allocation may not, depending on thekernel's memory overcommit handling configuration.)Note that running the tests under qemu will cause the expectedfailure, which is why this problem is not noticed by the CI.Simply disable these test on s390x. List of files: /wasmtime-44.0.1/tests/all/memory.rs Mon, 07 Apr 2025 17:19:28 +0000 Ulrich Weigand <ulrich.weigand@de.ibm.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#48f4621f Run the full test suite on 32-bit platforms (#9837)* Run the full test suite on 32-bit platformsThis commit switches to running the full test suite in its entirety(`./ci/run-tests.sh`) on 32-bit platforms in CI in addition to 64-bitplatforms. This notably adds i686 and armv7 as architectures that aretested in CI.Lots of little fixes here and there were applied to a number of tests.Many tests just don't run on 32-bit platforms or a platform withoutCranelift support, and they've been annotated as such where necessary.Other tests were adjusted to run on all platforms a few minor bug fixesare here as well.prtest:full* Fix clippy warning* Get wasm code working by default on 32-bitDon't require the `pulley` feature opt-in on 32-bit platforms to getwasm code running.* Fix dead code warning* Fix build on armv7* Fix test assertion on armv7* Review comments* Update how tests are skipped* Change how Pulley is defaultedDefault to pulley in `build.rs` rather than in `Cargo.toml` to make iteasier to write down the condition and comment what's happening. Thismeans that the `pulley-interpreter` crate and pulley support inCranelift is always compiled in now and cannot be removed. This shouldhopefully be ok though as the `pulley-interpreter` crate is stillconditionally used (meaning it can get GC'd) and the code-size ofCranelift is not as important as the runtime itself.* pulley: Save/restore callee-save state on traps* Fewer clippy warnings about casts* Use wrapping_add in `g32_addr`, fixing arm test List of files: /wasmtime-44.0.1/tests/all/memory.rs Wed, 15 Jan 2025 18:43:18 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#c42d92bf Fix some off-by-one comparisons in assertions (#9763)* Fix some off-by-one comparisons in assertionsFuzzing found a small issue with #9687 and this commit relaxes a fewoff-by-one checks to allow addressing one-byte-beyond-the-end of alinear memory.* Review comments List of files: /wasmtime-44.0.1/tests/all/memory.rs Tue, 10 Dec 2024 14:15:59 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#7a28a5b9 Remove static/dynamic memories from public docs (#9545)* Remove static/dynamic memories from public docsThis commit removes the terminology of "static" and "dynamic" memoriesfrom the public-facing documentation of Wasmtime, notably on the`Config` structure and its various configuration settings. The goal ofthis commit is in the same vein as #9543 which is to simplify the memorysettings of Wasmtime for users in this case.This change doesn't actually have any code changes beyond renames (andhandling now-deprecated CLI options). The goal of this commit is tobasically rewrite how we document the effect of various settings ofWasmtime. Notably:* `Config::static_memory_maximum_size` is now `memory_reservation`.* `Config::static_memory_forced` is now `memory_reservation_is_maximum`.* `Config::dynamic_memory_reserved_for_growth` is now `memory_reservation_for_growth`.Documentation for all of these options has been rewritten and updated totake into account the removal of "dynamic" and "static" terminology.Additionally more words have been written about the various effects ofeach setting and how things related to wasm features such as index typesizes and custom page sizes.The rewritten documentation is intended to basically already match whatWasmtime does today. I believe that all of these settings are useful inone form or another so none have been dropped but the updateddocumentation is intended to help simplify the mental model for howthey're processed internally and how they affect allocations and such.* Fix how the setting is flipped* Review comments List of files: /wasmtime-44.0.1/tests/all/memory.rs Tue, 05 Nov 2024 01:05:58 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#48d5338b Merge static/dynamic guard size options (#9528)* Merge static/dynamic guard size optionsThis commit is the first of what will likely be a few to refactor thememory-related configuration options in Wasmtime. The end goal of theserefactorings is to fix some preexisting issues and additionally make theconfiguration easier to understand for both users and implementorsalike. First on the chopping block here is to merge the`dynamic_memory_guard_size` and `static_memory_guard_size` options intoone option. AFAIK there's not a strong reason to have separateconfiguration options for these so it's hopefully simpler to have asingle `memory_guard_size` option which applies to all linear memoriesequally.I'll note that the old CLI options are preserved but are documented asdeprecated. We don't currently warn on using "deprecated options" so fornow the old options are just documented as deprecated and are otherwisesilently accepted.* Fix compilation of C API* Fix build of fuzzers List of files: /wasmtime-44.0.1/tests/all/memory.rs Fri, 01 Nov 2024 17:21:11 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#df69b9a7 Implement the table64 extension to the memory64 proposal (#9206)This commit implements the table64 extention in both Wasmtime andCranelift.Most of the work was changing a bunch of u32 values to u64/usize.The decisions were made in align with the PR #3153 whichimplemented the memory64 propsal itself.One significant change was the introduction of `IndexType`and `Limits` which streamline and unify the handling of limitsfor both memories and tables.The spec and fuzzing tests related to table64 are re-enabled whichprovides a good coverage of the feature. List of files: /wasmtime-44.0.1/tests/all/memory.rs Wed, 11 Sep 2024 17:34:31 +0000 Linwei Shang <github@lwshang.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#46098121 style: simplify string formatting (#9047)* style: simplify string formatting* fix: formatting in `benches/call.rs` List of files: /wasmtime-44.0.1/tests/all/memory.rs Wed, 31 Jul 2024 14:45:20 +0000 Hamir Mahal <hamirmahal@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#0e5048e2 winch: Consolidate memory tests in `test/all/memory.rs` (#8936)* winch: Consolidate memory tests in `test/all/memory.rs`This commit updates the memory tests to use`wasmtime_test_macros::wasmtime_test` where applicable. This changeconsolidates Winch's integration test suite into Wasmtime's generaltest suite.Note that this change doesn't update `wasmtime_test` to account forpooling allocation configuration. I can either update the macro in thisPR or do it as a follow-up change once we decide to migrate`tests/all/pooling_allocator.rs`.* Remove `winch` mod from `tests/main.rs` List of files: /wasmtime-44.0.1/tests/all/memory.rs Thu, 11 Jul 2024 00:04:36 +0000 Saúl Cabrera <saulecabrera@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#bdd78422 Wasmtime: Implement the custom-page-sizes proposal (#8763)* Wasmtime: Implement the custom-page-sizes proposalThis commit adds support for the custom-page-sizes proposal to Wasmtime:https://github.com/WebAssembly/custom-page-sizesI've migrated, fixed some bugs within, and extended the `*.wast` tests for thisproposal from the `wasm-tools` repository. I intend to upstream them into theproposal shortly.There is a new `wasmtime::Config::wasm_custom_page_sizes_proposal` method toenable or disable the proposal. It is disabled by default.Our fuzzing config has been updated to turn this feature on/off as dictated bythe arbitrary input given to us from the fuzzer.Additionally, there were getting to be so many constructors for`wasmtime::MemoryType` that I added a builder rather than add yet anotherconstructor.In general, we store the `log2(page_size)` rather than the page sizedirectly. This helps cut down on invalid states and properties we need toassert.I've also intentionally written this code such that supporting any power of twopage size (rather than just the exact values `1` and `65536` that are currentlyvalid) will essentially just involve updating `wasmparser`'s validation andremoving some debug asserts in Wasmtime.* Update error string expectation* Remove debug logging* Use a right shift instead of a division* fix error message expectation again* remove page size from VMMemoryDefinition* fix size of VMMemoryDefinition again* Only dynamically check for `-1` sentinel for 1-byte page sizes* Import functions that are used a few times* Better handle overflows when rounding up to the host page sizePropagate errors instead of returning a value that is not actually a rounded upversion of the input.Delay rounding up various config sizes until runtime instead of eagerly doing itat config time (which isn't even guaranteed to work, so we already had to have abackup plan to round up at runtime, since we might be cross-compiling wasm ornot have the runtime feature enabled).* Fix some anyhow and nostd errors* Add missing rounding up to host page size at runtime* Add validate feature to wasmparser dep* Add some new rounding in a few places, due to no longer rounding in config methods* Avoid actually trying to allocate the whole address space in the `massive_64_bit_still_limited` testThe point of the test is to ensure that we hit the limiter, so just cancel theallocation from the limiter, and otherwise avoid MIRI attempting to allocate abunch of memory after we hit the limiter.* prtest:full* Revert "Avoid actually trying to allocate the whole address space in the `massive_64_bit_still_limited` test"This reverts commit ccfa34a78dd3d53e49a6158ca03077d42ce8bcd7.* miri: don't attempt to allocate more than 4GiB of memoryIt seems that rather than returning a null pointer from `std::alloc::alloc`,miri will sometimes choose to simply crash the whole program.* remove duplicate prelude import after rebasing List of files: /wasmtime-44.0.1/tests/all/memory.rs Wed, 12 Jun 2024 21:46:42 +0000 Nick Fitzgerald <fitzgen@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#906ea017 Use bytes for maximum size of linear memory with pooling (#8628)* Use bytes for maximum size of linear memory with poolingThis commit changes configuration of the pooling allocator to use abyte-based unit rather than a page based unit. The previous`PoolingAllocatorConfig::memory_pages` configuration option configuresthe maximum size that a linear memory may grow to at runtime. This is animportant factor in calculation of stripes for MPK and is also acoarse-grained knob apart from `StoreLimiter` to limit memoryconsumption. This configuration option has been renamed to`max_memory_size` and documented that it's in terms of bytes rather thanpages as before.Additionally the documented constraint of `max_memory_size` must besmaller than `static_memory_bound` is now additionally enforced as aminor clean-up as part of this PR as well.* Review comments* Fix benchmark build List of files: /wasmtime-44.0.1/tests/all/memory.rs Fri, 17 May 2024 04:06:39 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#91ec9a58 Page align the static memory maximum size (#8630)This fixes an accidental regression from #8616 where page alignment wasimplicitly happening due to how configuration was processed but itwasn't re-added in the refactoring. List of files: /wasmtime-44.0.1/tests/all/memory.rs Wed, 15 May 2024 23:02:02 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#81a89169 Add support for `#![no_std]` to the `wasmtime` crate (#8533)* Always fall back to custom platform for WasmtimeThis commit updates Wasmtime's platform support to no longer require anopt-in `RUSTFLAGS` `--cfg` flag to be specified. With `no_std` becomingofficially supported this should provide a better onboarding experiencewhere the fallback custom platform is used. This will cause linkererrors if the symbols aren't implemented and searching/googling shouldlead back to our docs/repo (eventually, hopefully).* Change Wasmtime's TLS state to a single pointerThis commit updates the management of TLS to rely on just a singlepointer rather than a pair of a pointer and a `bool`. Additionallymanagement of the TLS state is pushed into platform-specific modules toenable different means of managing it, namely the "custom" platform nowhas a C function required to implement TLS state for Wasmtime.* Delay conversion to `Instant` in atomic intrinsicsThe `Duration` type is available in `no_std` but the `Instant` type isnot. The intention is to only support the `threads` proposal if `std` isactive but to assist with this split push the `Duration` further intoWasmtime to avoid using a type that can't be mentioned in `no_std`.* Gate more parts of Wasmtime on the `profiling` featureMove `serde_json` to an optional dependency and gate the guest profilerentirely on the `profiling` feature.* Refactor conversion to `anyhow::Error` in `wasmtime-environ`Have a dedicated trait for consuming `self` in addition to a`Result`-friendly trait.* Gate `gimli` in Wasmtime on `addr2line`Cut down the dependency list if `addr2line` isn't enabled since thenthe dependency is not used. While here additionally lift the versionrequirement for `addr2line` up to the workspace level.* Update `bindgen!` to have `no_std`-compatible outputPull most types from Wasmtime's `__internal` module as the source oftruth.* Use an `Option` for `gc_store` instead of `OnceCell`No need for synchronization here when mutability is already available inthe necessary contexts.* Enable embedder-defined host feature detection* Add `#![no_std]` support to the `wasmtime` crateThis commit enables compiling the `runtime`, `gc`, and `component-model`features of the `wasmtime` crate on targets that do not have `std`. Thistags the crate as `#![no_std]` and then updates everything internally toimport from `core` or `alloc` and adapt for the various idioms. Thisended up requiring some relatively extensive changes, but nothing tootoo bad in the grand scheme of things.* Require `std` for the perfmap profiling agentprtest:full* Fix build on wasm* Fix windows build* Remove unused import* Fix Windows/Unix build without `std` feature* Fix some doc links* Remove unused import* Fix build of wasi-common in isolation* Fix no_std build on macos* Re-fix build* Fix standalone build of wasmtime-cli-flags* Resolve a merge conflict* Review comments* Remove unused import List of files: /wasmtime-44.0.1/tests/all/memory.rs Sat, 04 May 2024 22:02:26 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/memory.rs#72004aad 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/tests/all/memory.rs Tue, 30 Apr 2024 18:52:45 +0000 Nick Fitzgerald <fitzgen@gmail.com>