en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/custom_code_memory.rs#94740588 Migrate the Wasmtime CLI to `wasmtime::error` (#12295)* Migrate wasmtime-cli to `wasmtime::error`* migrate benches to `wasmtime::error` as well* Remove new usage of anyhow that snuck in List of files: /wasmtime-44.0.1/tests/all/custom_code_memory.rs Fri, 09 Jan 2026 19:15:48 +0000 Nick Fitzgerald <fitzgen@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/custom_code_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/custom_code_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/custom_code_memory.rs#5eee6313 Wasmtime: support a notion of "custom code publisher". (#9778)* Wasmtime: support a notion of "custom code publisher".In some `no_std` environments, virtual memory usage is *generally*prohibited for performance-predictability reasons, but the MMUhardware is still in use for permissions (e.g., `W^X`write-xor-execute). Occasional changes to page mapping permissions arethus necessary when new modules are loaded dynamically, and areacceptable in that context. Wasmtime needs a way to support"publishing" code (making it executable) in such environments.Rather than try to segment the `signals-based-traps` divide further,and piece out the code-publishing parts from the heap parts, andbackdoor a path to `mprotect` in an otherwise `no_std` build, in thisPR I have opted to add a trait an impl of which the embedder canprovide to the `Config` to implement custom actions for "codepublish". This otherwise operates properly in ano-`signals-based-traps` environment, e.g., the module backing memoryitself is regularly allocated rather than mmap'd (but is now alignedto the degree requested by the trait impl).* Review feedback.* Plumb through custom alignment for runtime code generation* Add a test for custom code memory. List of files: /wasmtime-44.0.1/tests/all/custom_code_memory.rs Tue, 10 Dec 2024 23:56:25 +0000 Chris Fallin <chris@cfallin.org>