<?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 debug.rs</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>1d1c06f3 - Add basic support for profiling Pulley (#10034)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/pulley/src/interp/debug.rs#1d1c06f3</link>
        <description>Add basic support for profiling Pulley (#10034)* Add basic support for profiling PulleyThis commit adds basic support for profiling the Pulley interpreter.This is partially achievable previously through the use of nativeprofilers, but the downside of that approach is that you can find hotinstructions but it&apos;s not clear in what context the hot instructions arebeing executed nor what functions are hot. The goal of this profiler isto show pulley bytecode and time spent in bytecode itself to betterunderstand the shape of code around a hot instruction to identify newmacro opcodes for example.The general structure of this new profiler is:* There is a compile-time feature for Pulley which is off-by-default  where, when enabled, Pulley will record its current program counter  into an `AtomicUsize` before each instruction.* When the CLI has `--profile pulley` Wasmtime will spawn a sampling  thread in the same process which will periodically read from this  `AtomicUsize` to record where the program is currently executing.* The Pulley profiler additionally records all bytecode through the use  of the `ProfilingAgent` trait to ensure that the recording has access  to all bytecode as well.* Samples are taken throughout the process and emitted to a  `pulley-$pid.data` file. This file is then interpreted and printed by  an &quot;example&quot; program `profiler-html.rs` in the `pulley/examples`  directory.The end result is that hot functions of Pulley bytecode can be seen andinstructions are annotated with how frequently they were executed. Thisenables finding hot loops and understanding more about the whole loop,bytecodes that were selected, and such.* Add missing source file* Check the profile-pulley feature in CI* Miscellaneous fixes for CI* Fix type-checking of `become` on nightly Rust* Fix more misc CI issues* Fix dispatch in tail loop* Update test expectations* Review comments* Fix a feature combo

            List of files:
            /wasmtime-44.0.1/pulley/src/interp/debug.rs</description>
        <pubDate>Thu, 16 Jan 2025 22:49:36 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>c2fa8171 - pulley: Add simple debugging support (#9796)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/pulley/src/interp/debug.rs#c2fa8171</link>
        <description>pulley: Add simple debugging support (#9796)This commit adds a `debug.rs` to Pulley to print out the instructionbeing executed and the state of all registers between instructions. Thisis turned off by default and does not have a runtime orenvironment-based configuration value. Instead changing this requireschanging source code for now. This enables the interpreter loop tounconditionally use this &quot;debugger&quot; where it&apos;ll compile away to nothingin release/benchmarking situations.This commit additionally adds this support to the `tail_loop` module andfixes a few issues there such as it accidentally not being tested in CIas well as a new `#[cfg]` to use it on stable rust with normal `return`under the assumption that LLVM is highly likely to do TCO.

            List of files:
            /wasmtime-44.0.1/pulley/src/interp/debug.rs</description>
        <pubDate>Wed, 11 Dec 2024 23:07:14 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
</channel>
</rss>
