<?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 lib.rs</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>45b60bd6 - Start using `#[expect]` instead of `#[allow]` (#9696)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs#45b60bd6</link>
        <description>Start using `#[expect]` instead of `#[allow]` (#9696)* Start using `#[expect]` instead of `#[allow]`In Rust 1.81, our new MSRV, a new feature was added to Rust to use`#[expect]` to control lint levels. This new lint annotation willsilence a lint but will itself cause a lint if it doesn&apos;t actuallysilence anything. This is quite useful to ensure that annotations don&apos;tget stale over time.Another feature is the ability to use a `reason` directive on theattribute with a string explaining why the attribute is there. Thisstring is then rendered in compiler messages if a warning or errorhappens.This commit migrates applies a few changes across the workspace:* Some `#[allow]` are changed to `#[expect]` with a `reason`.* Some `#[allow]` have a `reason` added if the lint conditionally fires  (mostly related to macros).* Some `#[allow]` are removed since the lint doesn&apos;t actually fire.* The workspace configures `clippy::allow_attributes_without_reason = &apos;warn&apos;`  as a &quot;ratchet&quot; to prevent future regressions.* Many crates are annotated to allow `allow_attributes_without_reason`  during this transitionary period.The end-state is that all crates should use`#[expect(..., reason = &quot;...&quot;)]` for any lint that unconditionally firesbut is expected. The `#[allow(..., reason = &quot;...&quot;)]` lint should be usedfor conditionally firing lints, primarily in macro-related code.The `allow_attributes_without_reason = &apos;warn&apos;` level is intended to bepermanent but the transitionary`#[expect(clippy::allow_attributes_without_reason)]` crate annotationsto go away over time.* Fix adapter buildprtest:full* Fix one-core build of icache coherence* Use `allow` for missing_docsWork around rust-lang/rust#130021 which was fixed in Rust 1.83 and isn&apos;tfixed for our MSRV at this time.* More MSRV compat

            List of files:
            /wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs</description>
        <pubDate>Mon, 02 Dec 2024 17:19:20 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>c3f8415a - fuzz: improve the spec interpreter (#4881)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs#c3f8415a</link>
        <description>fuzz: improve the spec interpreter (#4881)* fuzz: improve the API of the `wasm-spec-interpreter` crateThis change addresses key parts of #4852 by improving the bindings tothe OCaml spec interpreter. The new API allows users to `instantiate` amodule, `interpret` named functions on that instance, and `export`globals and memories from that instance. This currently leaves theexisting implementation (&quot;instantiate and interpret the first function ina module&quot;) present under a new name: `interpret_legacy`.* fuzz: adapt the differential spec engine to the new APIThis removes the legacy uses in the differential spec engine, replacingthem with the new `instantiate`-`interpret`-`export` API from the`wasm-spec-interpreter` crate.* fix: make instance access thread-safeThis changes the OCaml-side definition of the instance so that eachinstance carries round a reference to a &quot;global store&quot; that&apos;s specificto that instantiation. Because everything is updated by reference thereshould be no visible behavioural change on the Rust side, apart fromeverything suddenly being thread-safe (modulo the fact that access tothe OCaml runtime still needs to be locked). This fix will need to begeneralised slightly in future if we want to allow multiple modules tobe instantiated in the same store.Co-authored-by: conrad-watt &lt;cnrdwtt@gmail.com&gt;Co-authored-by: Alex Crichton &lt;alex@alexcrichton.com&gt;

            List of files:
            /wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs</description>
        <pubDate>Mon, 12 Sep 2022 21:23:03 +0000</pubDate>
        <dc:creator>Andrew Brown &lt;andrew.brown@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>fd98814b - Port v8 fuzzer to the new framework (#4739)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs#fd98814b</link>
        <description>Port v8 fuzzer to the new framework (#4739)* Port v8 fuzzer to the new frameworkThis commit aims to improve the support for the new &quot;meta&quot; differentialfuzzer added in #4515 by ensuring that all existing differential fuzzingis migrated to this new fuzzer. This PR includes features such as:* The V8 differential execution is migrated to the new framework.* `Config::set_differential_config` no longer force-disables wasm  features, instead allowing them to be enabled as per the fuzz input.* `DiffInstance::{hash, hash}` was replaced with  `DiffInstance::get_{memory,global}` to allow more fine-grained  assertions.* Support for `FuncRef` and `ExternRef` have been added to `DiffValue`  and `DiffValueType`. For now though generating an arbitrary  `ExternRef` and `FuncRef` simply generates a null value.* Arbitrary `DiffValue::{F32,F64}` values are guaranteed to use  canonical NaN representations to fix an issue with v8 where with the  v8 engine we can&apos;t communicate non-canonical NaN values through JS.* `DiffEngine::evaluate` allows &quot;successful failure&quot; for cases where  engines can&apos;t support that particular invocation, for example v8 can&apos;t  support `v128` arguments or return values.* Smoke tests were added for each engine to ensure that a simple wasm  module works at PR-time.* Statistics printed from the main fuzzer now include percentage-rates  for chosen engines as well as percentage rates for styles-of-module.There&apos;s also a few small refactorings here and there but mostly justthings I saw along the way.* Update the fuzzing README

            List of files:
            /wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs</description>
        <pubDate>Fri, 19 Aug 2022 19:19:00 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>c8daf0b8 - support SIMD fuzzing in reference interpreter (#3980)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs#c8daf0b8</link>
        <description>support SIMD fuzzing in reference interpreter (#3980)* support SIMD fuzzing in reference interpreter* formatting

            List of files:
            /wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs</description>
        <pubDate>Thu, 31 Mar 2022 15:07:39 +0000</pubDate>
        <dc:creator>Conrad Watt &lt;cnrdwtt@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>98ef18a2 - Fuzzing against verified fork of spec interpreter (#3843)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs#98ef18a2</link>
        <description>Fuzzing against verified fork of spec interpreter (#3843)* Revert &quot;Remove spec interpreter fuzz target temporarily (#3399)&quot;This reverts commit 25d3fa4d7b944b4341928a401c57feaaa0ce3c35.* add support for differential fuzzing against verified OCaml interpreter* formatting* comments* fix missing dep case* fix build error* fix unit tests?* restore previous differential_v8 max_table config* attempt: add OCaml deps* fix interpeter github repo* fix spec repo url* fix zarith package* fix unit test

            List of files:
            /wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs</description>
        <pubDate>Tue, 01 Mar 2022 18:01:46 +0000</pubDate>
        <dc:creator>Conrad Watt &lt;cnrdwtt@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>25d3fa4d - Remove spec interpreter fuzz target temporarily (#3399)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs#25d3fa4d</link>
        <description>Remove spec interpreter fuzz target temporarily (#3399)This commit removes the `differential_spec` fuzz target for now,although this removal is intended to be temporary. We have #3251 totrack re-enabling the spec interpreter in a way that it won&apos;t time out,and additionally the spec interpreter is also failing to build withocaml on oss-fuzz so that will also need to be investigated whenre-enabling.

            List of files:
            /wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs</description>
        <pubDate>Thu, 30 Sep 2021 18:09:19 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>a7f592a0 - Add a crate to interface with the WebAssembly spec interpreter</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs#a7f592a0</link>
        <description>Add a crate to interface with the WebAssembly spec interpreterThe WebAssembly spec interpreter is written in OCaml and the new crateuses `ocaml-interop` along with a small OCaml wrapper to interpret Wasmmodules in-process. The build process for this crate is currentlyLinux-specific: it requires several OCaml packages (e.g. `apt install -yocaml-nox ocamlbuild`) as well as `make`, `cp`, and `ar`.

            List of files:
            /wasmtime-44.0.1/crates/fuzzing/wasm-spec-interpreter/src/lib.rs</description>
        <pubDate>Wed, 28 Jul 2021 20:12:47 +0000</pubDate>
        <dc:creator>Andrew Brown &lt;andrew.brown@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
