<?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 .gitattributes</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>7682a40d - `generated-code.rs` is not itself generated code (#5571)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/.gitattributes#7682a40d</link>
        <description>`generated-code.rs` is not itself generated code (#5571)cranelift/codegen/src/isa/*/lower/isle/generated_code.rs arehand-written modules that `include!` the actual generated code.Tagging these hand-written files as `linguist-generated` in.gitattributes tells GitHub not to show them in diffs by default. Butthey&apos;re actually important to review, so they should be included indiffs.

            List of files:
            /wasmtime-44.0.1/.gitattributes</description>
        <pubDate>Fri, 13 Jan 2023 19:03:50 +0000</pubDate>
        <dc:creator>Jamey Sharp &lt;jsharp@fastly.com&gt;</dc:creator>
    </item>
<item>
        <title>1141169f - aarch64: Initial work to transition backend to ISLE (#3541)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/.gitattributes#1141169f</link>
        <description>aarch64: Initial work to transition backend to ISLE (#3541)* aarch64: Initial work to transition backend to ISLEThis commit is what is hoped to be the initial commit towards migratingthe aarch64 backend to ISLE. There&apos;s seemingly a lot of changes here butit&apos;s intended to largely be code motion. The current thinking is toclosely follow the x64 backend for how all this is handled andorganized.Major changes in this PR are:* The `Inst` enum is now defined in ISLE. This avoids having to define  it in two places (once in Rust and once in ISLE). I&apos;ve preserved all  the comments in the ISLE and otherwise this isn&apos;t actually a  functional change from the Rust perspective, it&apos;s still the same enum  according to Rust.* Lots of little enums and things were moved to ISLE as well. As with  `Inst` their definitions didn&apos;t change, only where they&apos;re defined.  This will give future ISLE PRs access to all these operations.* Initial code for lowering `iconst`, `null`, and `bconst` are  implemented. Ironically none of this is actually used right now  because constant lowering is handled in `put_input_in_regs` which  specially handles constants. Nonetheless I wanted to get at least  something simple working which shows off how to special case various  things that are specific to AArch64. In a future PR I plan to hook up  const-lowering in ISLE to this path so even though  `iconst`-the-clif-instruction is never lowered this should use the  const lowering defined in ISLE rather than elsewhere in the backend  (eventually leading to the deletion of the non-ISLE lowering).* The `IsleContext` skeleton is created and set up for future additions.* Some code for ISLE that&apos;s shared across all backends now lives in  `isle_prelude_methods!()` and is deduplicated between the AArch64  backend and the x64 backend.* Register mapping is tweaked to do the same thing for AArch64 that it  does for x64. Namely mapping virtual registers is supported instead of  just virtual to machine registers.My main goal with this PR was to get AArch64 into a place where newinstructions can be added with relative ease. Additionally I&apos;m hoping tofigure out as part of this change how much to share for ISLE betweenAArch64 and x64 (and other backends).* Don&apos;t use priorities with rules* Update .gitattributes with concise syntax* Deduplicate some type definitions* Rebuild ISLE* Move isa::isle to machinst::isle

            List of files:
            /wasmtime-44.0.1/.gitattributes</description>
        <pubDate>Thu, 18 Nov 2021 16:38:16 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>d377b665 - Initial ISLE integration with the x64 backend</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/.gitattributes#d377b665</link>
        <description>Initial ISLE integration with the x64 backendOn the build side, this commit introduces two things:1. The automatic generation of various ISLE definitions for working withCLIF. Specifically, it generates extern type definitions for clif opcodes andthe clif instruction data `enum`, as well as extractors for matching each clifinstructions. This happens inside the `cranelift-codegen-meta` crate.2. The compilation of ISLE DSL sources to Rust code, that can be included in themain `cranelift-codegen` compilation.Next, this commit introduces the integration glue code required to getISLE-generated Rust code hooked up in clif-to-x64 lowering. When lowering a clifinstruction, we first try to use the ISLE code path. If it succeeds, then we aredone lowering this instruction. If it fails, then we proceed along the existinghand-written code path for lowering.Finally, this commit ports many lowering rules over from hand-written,open-coded Rust to ISLE.In the process of supporting ISLE, this commit also makes the x64 `Inst` capableof expressing SSA by supporting 3-operand forms for all of the existinginstructions that only have a 2-operand form encoding:    dst = src1 op src2Rather than only the typical x86-64 2-operand form:    dst = dst op srcThis allows `MachInst` to be in SSA form, since `dst` and `src1` aredisentangled.(&quot;3-operand&quot; and &quot;2-operand&quot; are a little bit of a misnomer since not alloperations are binary operations, but we do the same thing for, e.g., unaryoperations by disentangling the sole operand from the result.)There are two motivations for this change:1. To allow ISLE lowering code to have value-equivalence semantics. We want ISLE   lowering to translate a CLIF expression that evaluates to some value into a   `MachInst` expression that evaluates to the same value. We want both the   lowering itself and the resulting `MachInst` to be pure and referentially   transparent. This is both a nice paradigm for compiler writers that are   authoring and maintaining lowering rules and is a prerequisite to any sort of   formal verification of our lowering rules in the future.2. Better align `MachInst` with `regalloc2`&apos;s API, which requires that the input   be in SSA form.

            List of files:
            /wasmtime-44.0.1/.gitattributes</description>
        <pubDate>Wed, 13 Oct 2021 00:11:58 +0000</pubDate>
        <dc:creator>Nick Fitzgerald &lt;fitzgen@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>c202a8ee - Add a .gitattributes file to specify eol=LF (#1370)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/.gitattributes#c202a8ee</link>
        <description>Add a .gitattributes file to specify eol=LF (#1370)* Add a .gitattributes file specifying LF-style line endings.This is similar to [Rust&apos;s .gitattributes file] though simplified.Most of our source and documentation files already used LF-style lineendings, including *.cs files, so this makes things more consistent.[Rust&apos;s .gitattributes file]: https://github.com/rust-lang/rust/blob/master/.gitattributes* Remove UTF-8 BOMs in *.cs files.Most of our *.cs files don&apos;t have UTF-8 BOMs, so this makes things moreconsistent.

            List of files:
            /wasmtime-44.0.1/.gitattributes</description>
        <pubDate>Sat, 21 Mar 2020 01:36:13 +0000</pubDate>
        <dc:creator>Dan Gohman &lt;sunfish@mozilla.com&gt;</dc:creator>
    </item>
</channel>
</rss>
