<?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 simple.wast</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>e50d897b - Add `bulk_memory` to wast configuration (#12883)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast#e50d897b</link>
        <description>Add `bulk_memory` to wast configuration (#12883)Allows enabling/disabling this wasm proposal on a per-test basis.

            List of files:
            /wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast</description>
        <pubDate>Mon, 30 Mar 2026 12:44:15 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>60fc557c - Refactor how wasm features are calculated for `*.wast` tests (#9560)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast#60fc557c</link>
        <description>Refactor how wasm features are calculated for `*.wast` tests (#9560)* Refactor how wasm features are calculated for `*.wast` testsThis commit refactors the `tests/wast.rs` test suite which runs all ofthe upstream spec tests as `*.wast` files as well as our own`misc_testsuite` which has its own suite of `*.wast` files. Previouslythe set of wasm features active for each test was a sort of randommishmash and convoluted set of conditionals which was updated and editedover time as upstream proposal test suites evolved. This was thenmirrored into our own conventions for `misc_testsuite` as well. Overallthough this has a number of downsides I&apos;m trying to fix here:* The calculation of what features are enabled is quite complicated and  effectively a random mishmash of `||` conditionals with hierarchies  that don&apos;t make any sense beyond &quot;this is just required to get things  to pass&quot;.* There is no means of per-test configuration. For example  `canonicalize-nans.wast` had hardcoded logic in `tests/wast.rs` that  it needed a different setting turned on in `Config`.* There was no easy means to write tests for Wasmtime which take a union  of a number of proposals together without having lots of sub-folders  that may not make sense.* Tests that require a particular proposal had to have duplicate logic  for Winch as it doesn&apos;t support the full suite of features of all  proposals that Cranelift does.The new system implemented in this commit takes a leaf out of the`disas` tests. There is a new `TestConfig` structure in the`tests/wast.rs` harness which is decoded from each test (leading `;;!`comments) which enables specifying, in each test, what&apos;s required. Thisencompasses many wasm proposals but additionally captures other behaviorlike nan-canonicalization. This means that all test files in`misc_testsuite/**/*.wast` are now manually annotated with what wasmfeatures they require and what&apos;s needed to run. This makes per-testconfiguration much easier, per-config-setting much easier, and blanketignore-by-proposal for Winch much easier as well.For spec tests we can&apos;t modify the contents of the upstream `*.wast`files. To handle this they&apos;re handled specially where `TestConfig` ismanually created and manipulated for each spec proposal and the maintest suite itself. This enables per-proposal configuration that doesn&apos;tleak into any others and makes it more obvious what proposals are doingwhat.* Hack around Winch support for aarch64

            List of files:
            /wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast</description>
        <pubDate>Tue, 05 Nov 2024 21:26:25 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>89ccc56e - Update the wasm-tools family of crates (#4165)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast#89ccc56e</link>
        <description>Update the wasm-tools family of crates (#4165)* Update the wasm-tools family of cratesThis commit updates these crates as used by Wasmtime for the recentlypublished versions to pull in changes necessary to support the componentmodel. I&apos;ve split this out from #4005 to make it clear what&apos;s impactedhere and #4005 can simply rebase on top of this to pick up the necessarychanges.* More test fixes

            List of files:
            /wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast</description>
        <pubDate>Thu, 19 May 2022 19:13:04 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>65486a06 - Update wasm-tools crates</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast#65486a06</link>
        <description>Update wasm-tools cratesNothing major here, just a routine update with a few extra things tohandle here-and-there.

            List of files:
            /wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast</description>
        <pubDate>Wed, 02 Feb 2022 17:45:43 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>4a351ab7 - Update a number of dependencies (#2594)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast#4a351ab7</link>
        <description>Update a number of dependencies (#2594)This commit goes through the dependencies that wasmtime has and updatesversions where possible. This notably brings in a wasmparser/wast updatewhich has some simd spec changes with new instructions. Otherwise mostof these are just routine updates.

            List of files:
            /wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast</description>
        <pubDate>Thu, 21 Jan 2021 21:49:13 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>e659d5ce - Add initial support for the multi-memory proposal (#2263)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast#e659d5ce</link>
        <description>Add initial support for the multi-memory proposal (#2263)This commit adds initial (gated) support for the multi-memory wasmproposal. This was actually quite easy since almost all of wasmtimealready expected multi-memory to be implemented one day. The only realsubstantive change is the `memory.copy` intrinsic changes, which nowaccounts for the source/destination memories possibly being different.

            List of files:
            /wasmtime-44.0.1/tests/misc_testsuite/multi-memory/simple.wast</description>
        <pubDate>Wed, 14 Oct 2020 00:13:52 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
</channel>
</rss>
