<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in README.md</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>7f9049b9 - Replace `signals-based-traps` with auto-detection (#9941)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/examples/min-platform/README.md#7f9049b9</link>
        <description>Replace `signals-based-traps` with auto-detection (#9941)* Replace `signals-based-traps` with auto-detectionThis commit refactors the platform support of the `wasmtime` crateitself to remove the previously added `signals-based-traps` feature infavor of auto-detecting whether it&apos;s there or not. The `build.rs`script for the `wasmtime` crate will now detect the target platform andauto-enable this feature as necessary.The `signals-based-traps` cargo feature is removed and split into twocustom `#[cfg]` directives that the build script sets:* `has_virtual_memory` - this is used to gate mmap implementations for  example. This is enabled on `unix || windows` and will be off for  `no_std` targets for example. This is split out of  &quot;signals-based-traps&quot; to better handle platforms like iOS which have  virtual memory but don&apos;t execute native code (removing the need for  native signals).* `has_native_signals` - gates signal handlers on Unix for example. This  is disabled on MIRI but otherwise enabled for `unix || windows`. This  is intended to in the future get disabled for iOS by default for  example since it&apos;s not necessary when using Pulley. This is  additionally off-by-default for `no_std` platforms.Two new crate features were added for `no_std` or &quot;custom&quot; platforms toopt-in to the `wasmtime-platform.h` C APIs for implementing virtualmemory and signals. These are used in the `min-platform` embedding example.This commit additionally updates some various documentation here andthere to be more up-to-date.* Update CI configuration* Fix compile warnings* Fix test on miri* Fix more tests on miri* Fix some warnings* Another round of miri/CI attempts/fixesprtest:full

            List of files:
            /wasmtime-44.0.1/examples/min-platform/README.md</description>
        <pubDate>Wed, 15 Jan 2025 01:15:14 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>72004aad - Turn the `wasmtime-runtime` crate into the `wasmtime::runtime::vm` module (#8501)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/examples/min-platform/README.md#72004aad</link>
        <description>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/examples/min-platform/README.md</description>
        <pubDate>Tue, 30 Apr 2024 18:52:45 +0000</pubDate>
        <dc:creator>Nick Fitzgerald &lt;fitzgen@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b81bb7a3 - Add a &quot;custom&quot; platform configuration for Wasmtime (#7995)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/examples/min-platform/README.md#b81bb7a3</link>
        <description>Add a &quot;custom&quot; platform configuration for Wasmtime (#7995)* Add a &quot;custom&quot; platform configuration for WasmtimeThis commit leverages adds a new &quot;platform&quot; to Wasmtime to be supportedin the `crates/runtime/src/sys` folder. This joins preexisting platformssuch as Unix and Windows. The goal of this platform is to be an opt-inway to build Wasmtime for targets that don&apos;t have a predefined way torun.The new &quot;custom&quot; platform requires `--cfg wasmtime_custom_platform` tobe passed to the Rust compiler, for example by using `RUSTFLAGS`. Thisnew platform bottoms out in a C API that is intended to be small andLinux-like. The C API is effectively the interface to virtual memorythat Wasmtime requires. This C API is also available as a header file at`examples/min-platform/embedding/wasmtime-platform.h` (generated by`cbindgen`).The main purpose of this is to make it easier to experiment with portingWasmtime to new platforms. By decoupling a platform implementation fromWasmtime itself it should be possible to run these experimentsout-of-tree. An example of this I&apos;ve been working on is gettingWasmtime running on bare-metal with a custom kernel. This supportenables defining the platform interface of the custom kernel&apos;s syscallsoutside of Wasmtime.* Exclude wasmtime-platform.h from formatting* Include build-wasmtime-target-wasm32 in final job* Don&apos;t force any single toolchain* Add notes to no_std docs* Add rust-src to CI* Review comments* Change APIs to be fallible* Only compile the min-platform example on Linux* Fix compile of min-platform example* Fix another compile error in the example

            List of files:
            /wasmtime-44.0.1/examples/min-platform/README.md</description>
        <pubDate>Wed, 28 Feb 2024 20:23:33 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
</channel>
</rss>
