From 1eed0bcb89e7b6ea9f74a5ff3d0bf9688f3d2d8b Mon Sep 17 00:00:00 2001 From: Alex Crichton Date: Wed, 20 Apr 2022 12:44:57 -0500 Subject: [PATCH] Add some release notes for 0.37.0 (#4056) I was poking at the release process so figured I'd do some release notes touch-up as well. --- RELEASES.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/RELEASES.md b/RELEASES.md index 0ce77a30a7..5f2aec934b 100644 --- a/RELEASES.md +++ b/RELEASES.md @@ -15,12 +15,32 @@ Unreleased. artifacts. [#3983](https://github.com/bytecodealliance/wasmtime/pull/3983) +* Copy-on-write images of memory can now be manually initialized for a `Module` + with an explicit method call, but it is still not required to call this method + and will automatically otherwise happen on the first instantiation. + [#3964](https://github.com/bytecodealliance/wasmtime/pull/3964) + ### Fixed * Using `InstancePre::instantiate` or `Linker::instantiate` will now panic as intended when used with an async-configured `Store`. [#3972](https://github.com/bytecodealliance/wasmtime/pull/3972) +### Changed + +* The unsafe `ValRaw` type in the `wasmtime` crate now always stores its values + in little-endian format instead of the prior native-endian format. Users of + `ValRaw` are recommended to audit their existing code for usage to continue + working on big-endian platforms. + [#4035](https://github.com/bytecodealliance/wasmtime/pull/4035) + +### Removed + +* Support for `Config::paged_memory_initialization` and the `uffd` crate feature + have been removed from the `wasmtime` crate. Users should migrate to using + `Config::memory_init_cow` which is more portable and faster at this point. + [#4040](https://github.com/bytecodealliance/wasmtime/pull/4040) + -------------------------------------------------------------------------------- ## 0.36.0