<?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 examples-pulley.md</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>eed7c104 - pulley: Allow disabling SIMD in the interpreter at compile-time (#10727)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/examples-pulley.md#eed7c104</link>
        <description>pulley: Allow disabling SIMD in the interpreter at compile-time (#10727)This commit adds a new feature to Pulley which is used to reduce thecompiled code size of the interpreter itself by disabling SIMD opcodeinterpretation at compile-time. The goal here is to be low-impact onPulley itself to avoid needing `#[cfg]` all over the place and toadditionally avoid the need to redesign Pulley&apos;s opcode macro for use invarious parts of Wasmtime.Methods are annotated with a custom macro in the interpreter whichregisters a `#[cfg]` that either does the listed implementation orswitches to an implementation that emits a trap if executed. This meansthat it&apos;s safe to execute mismatched code where SIMD was enabled atcompile time but disabled at runtime, it just means the semantics may bea bit surprising to debug.Note that this SIMD is still enabled by default, and an explicit `--cfg`via `RUSTFLAGS` is required to compile-out the SIMD support. Cargofeatures aren&apos;t a great fit for this sort of feature so an explicit flagis used.

            List of files:
            /wasmtime-44.0.1/docs/examples-pulley.md</description>
        <pubDate>Mon, 05 May 2025 20:34:13 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>92cfda1b - refactor(docs): more conversions of sh to console for copy-paste (#10707)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/examples-pulley.md#92cfda1b</link>
        <description>refactor(docs): more conversions of sh to console for copy-paste (#10707)This commit udpates more instructions on various READMEs to avoid `$`for easy copy-pasting, and also use `console` where appropriate.Signed-off-by: Victor Adossi &lt;vadossi@cosmonic.com&gt;

            List of files:
            /wasmtime-44.0.1/docs/examples-pulley.md</description>
        <pubDate>Fri, 02 May 2025 14:44:25 +0000</pubDate>
        <dc:creator>Victor Adossi &lt;123968127+vados-cosmonic@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>54988feb - Add a bunch of cookbook-style &quot;how do I do X?&quot; examples to the book (#10630)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/examples-pulley.md#54988feb</link>
        <description>Add a bunch of cookbook-style &quot;how do I do X?&quot; examples to the book (#10630)This tries to cover things that we repeatedly get questions about on Zulip.

            List of files:
            /wasmtime-44.0.1/docs/examples-pulley.md</description>
        <pubDate>Tue, 22 Apr 2025 00:43:30 +0000</pubDate>
        <dc:creator>Nick Fitzgerald &lt;fitzgen@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>3e406d2e - Add a `wasmtime objdump` subcommand (#10405)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/examples-pulley.md#3e406d2e</link>
        <description>Add a `wasmtime objdump` subcommand (#10405)This commit adds an `objdump` subcommand to the `wasmtime` CLI. Like allother subcommands this can be disabled for a more minimal build of theCLI as well. The purpose of this subcommand is to provide aWasmtime-specific spin on the venerable native `objdump` itself. Notablythis brings Wasmtime-specific knowledge for filtering functions, showingWasmtime metadata, etc.This command is intended to look like `objdump` roughly but also hasconfigurable output with various flags and things that can be printed.For now the main Wasmtime additions are showing the address mapsection, stack map section, and trap section of a `*.cwasm` file.This new subcommand replaces the infrastructure of the `disas` testsuite, and now that test suite uses `wasmtime objdump` to generate testexpectations. Additionally the subcommand replaces the Pulley `objdump`example as a more full-featured objdump that also works natively withPulley.The hope is that if we add more binary metadata in the future (such asunwinding tables) that can be relatively easily added here forexploration as well. Otherwise this is mostly just a developerconvenience for Wasmtime developers as well and hopefully doesn&apos;t costtoo much in maintenance burden.Closes #10336

            List of files:
            /wasmtime-44.0.1/docs/examples-pulley.md</description>
        <pubDate>Thu, 20 Mar 2025 19:23:59 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>8a969897 - Add book-level documentation for Pulley (#10095)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/examples-pulley.md#8a969897</link>
        <description>Add book-level documentation for Pulley (#10095)* Add book-level documentation for PulleyThis commit adds some longer form documentation about Pulley inWasmtime&apos;s online documentation book. This covers topics such as:* What is Pulley?* How to enable Pulley?* What happens when using Pulley.* Advantages/disadvantages of Pulley.* High-level design of Pulley.* Decompiling `*.cwasm` Pulley opcodes.* Profiling Pulley.* Update docs/examples-pulley.mdCo-authored-by: Joel Dice &lt;joel.dice@fermyon.com&gt;* Don&apos;t test examples---------Co-authored-by: Joel Dice &lt;joel.dice@fermyon.com&gt;

            List of files:
            /wasmtime-44.0.1/docs/examples-pulley.md</description>
        <pubDate>Thu, 23 Jan 2025 23:08:42 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
</channel>
</rss>
