<?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 empty-module.wat</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>57cd5a9e - Start plumbing the ability to run Pulley in Wasmtime (#9646)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/all/cli_tests/empty-module.wat#57cd5a9e</link>
        <description>Start plumbing the ability to run Pulley in Wasmtime (#9646)* Start plumbing the ability to run Pulley in WasmtimeThis commit starts setting up some infrastructure to run Pulley modulesin Wasmtime, for example on the CLI. This doesn&apos;t actually work just yetdue to other missing pieces of integration but this is enough to get toa fault and/or other compiler errors at this time. The changes here are:* An `Engine` allows mismatching targets in the case of Pulley, but the  pointer widths must match.* All subcommands of Wasmtime now support `--target`, e.g. `wasmtime  run`, as previously only the host was allowed.* Fix compile of bench-api* Fix miri tests* Switch from `NativeEndian` to `Endianness`This switches parsing ELF from always using the native endianness toinstead using a runtime-defined value of endianness. This enablesbig-endian platforms such as s390x to load objects produced for pulley,a little-endian platform.

            List of files:
            /wasmtime-44.0.1/tests/all/cli_tests/empty-module.wat</description>
        <pubDate>Thu, 21 Nov 2024 19:50:51 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
</channel>
</rss>
