<?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 byte_count.rs</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>9034e101 - Rely on `core::error::Error` (#9702)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/byte_count.rs#9034e101</link>
        <description>Rely on `core::error::Error` (#9702)* Rely on `core::error::Error`With Wasmtime&apos;s new MSRV at 1.81 this means that `core::error::Error` isavailable which means that in `no_std` mode the `Error` trait can beused. This has been integrated into `anyhow::Error` already upstream andmeans that we can remove our own local hacks such as the `Err2Anyhow` trait.This commit removes the `Err2Anyhow` trait and all usage, going back toidiomatic Rust error propagation and conversion even in the `no_std`world. This should make code more portable by default and remove someweird idioms we had for supporting this.prtest:full* Add some trusted vets* Audit object crate update* Disable backtraces on CI

            List of files:
            /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/byte_count.rs</description>
        <pubDate>Tue, 03 Dec 2024 18:27:28 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>d5db7a68 - Move memory pool over to aligned byte counts (#9668)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/byte_count.rs#d5db7a68</link>
        <description>Move memory pool over to aligned byte counts (#9668)* Move memory pool over to aligned byte countsPart of work to centralize memory management within Mmap instances -- some ofthat work becomes easier if the byte counts are known to be aligned.There were a few overflow cases that I added checks for.* Address review comments* Fix unused code warnings

            List of files:
            /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/byte_count.rs</description>
        <pubDate>Mon, 25 Nov 2024 20:15:56 +0000</pubDate>
        <dc:creator>Rain &lt;rain@sunshowers.io&gt;</dc:creator>
    </item>
<item>
        <title>74a703b2 - Add HostAlignedByteCount to enforce alignment at compile time (#9620)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/byte_count.rs#74a703b2</link>
        <description>Add HostAlignedByteCount to enforce alignment at compile time (#9620)* Add HostAlignedByteCount to enforce alignment at compile timeAs part of the work to allow mmaps to be backed by other implementations, Irealized that we didn&apos;t have any way to track whether a particular usize ishost-page-aligned at compile time.Add a `HostAlignedByteCount` which tracks that a particular usize is aligned tothe host page size. This also does not expose safe unchecked arithmeticoperations, to ensure that overflows always error out.With `HostAlignedByteCount`, a lot of runtime checks can go away thanks to thetype-level assertion.In the interest of keeping the diff relatively small, I haven&apos;t convertedeverything over yet. More can be converted over as time permits.* Make zero-sized mprotects a no-op, add tests

            List of files:
            /wasmtime-44.0.1/crates/wasmtime/src/runtime/vm/byte_count.rs</description>
        <pubDate>Fri, 22 Nov 2024 00:23:19 +0000</pubDate>
        <dc:creator>Rain &lt;rain@sunshowers.io&gt;</dc:creator>
    </item>
</channel>
</rss>
