<?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 engine.h</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>cb51a4f2 - Enable introspecting pulley at runtime (#9886)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/engine.h#cb51a4f2</link>
        <description>Enable introspecting pulley at runtime (#9886)This commit includes a few assorted changes to improve detection ofwhether Wasmtime is using Pulley at runtime:* A new `Engine::is_pulley` API is added.* A new `wasmtime_engine_is_pulley` C API is added.* The `Config::target` method is now available regardless of compilation  features.* The `Engine::target` method now consults the `Config` to have the same  fallback logic for when a target is not explicitly configured.cc #1980

            List of files:
            /wasmtime-44.0.1/crates/c-api/include/wasmtime/engine.h</description>
        <pubDate>Mon, 30 Dec 2024 19:51:45 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
<item>
        <title>9e22c4e7 - Expose Engine::clone to c-api (#8907)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/engine.h#9e22c4e7</link>
        <description>Expose Engine::clone to c-api (#8907)

            List of files:
            /wasmtime-44.0.1/crates/c-api/include/wasmtime/engine.h</description>
        <pubDate>Mon, 08 Jul 2024 14:34:23 +0000</pubDate>
        <dc:creator>Ryan Patterson &lt;cgamesplay@cgamesplay.com&gt;</dc:creator>
    </item>
<item>
        <title>f8fee938 - add clang format (#7601)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/engine.h#f8fee938</link>
        <description>add clang format (#7601)* add clang-formatWe chose WebKit style because out of all the builtin styles it seems theclosest to what already exists in wasmtime.Signed-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* c-api: don&apos;t reorder headersThe order here mattersSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* c-api: apply clang-formatSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* fiber: apply clang-formatSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* runtime: apply clang-formatSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* examples: apply clang formatSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* tests: apply clang-formatSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* ci: add clang-format checksSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* clang-format: keep braces on the same lineThis is more the existing styleSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* remove clang-formatJust use the tool defaults (LLVM)Signed-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* Fix ci nameSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* manually reformat a couple of commentsprtest:fullSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* disable formatting for doc-wasm.hSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* manually reformat wasmtime.hSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* disable formattingTo prevent a link from being brokenSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* examples: fixing build commandsSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;* fix parameter commentSigned-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;---------Signed-off-by: Tyler Rockwood &lt;rockwood@redpanda.com&gt;

            List of files:
            /wasmtime-44.0.1/crates/c-api/include/wasmtime/engine.h</description>
        <pubDate>Wed, 29 Nov 2023 18:39:04 +0000</pubDate>
        <dc:creator>Tyler Rockwood &lt;rockwotj@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>c22033bf - Delete historical interruptable support in Wasmtime (#3925)</title>
        <link>http://172.16.0.5:8080/history/wasmtime-44.0.1/crates/c-api/include/wasmtime/engine.h#c22033bf</link>
        <description>Delete historical interruptable support in Wasmtime (#3925)* Delete historical interruptable support in WasmtimeThis commit removes the `Config::interruptable` configuration along withthe `InterruptHandle` type from the `wasmtime` crate. The originalsupport for adding interruption to WebAssembly was added pretty early onin the history of Wasmtime when there was no other method to prevent aninfinite loop from the host. Nowadays, however, there are alternativemethods for interruption such as fuel or epoch-based interruption.One of the major downsides of `Config::interruptable` is that even whenit&apos;s not enabled it forces an atomic swap to happen when enteringWebAssembly code. This technically could be a non-atomic swap if theconfiguration option isn&apos;t enabled but that produces even more branch-ycode on entry into WebAssembly which is already something we try tooptimize. Calling into WebAssembly is on the order of a dozens ofnanoseconds at this time and an atomic swap, even uncontended, can addup to 5ns on some platforms.The main goal of this PR is to remove this atomic swap on entry intoWebAssembly. This is done by removing the `Config::interruptable` fieldentirely, moving all existing consumers to epochs instead which aresuitable for the same purposes. This means that the stack overflow checkis no longer entangled with the interruption check and perhaps one daywe could continue to optimize that further as well.Some consequences of this change are:* Epochs are now the only method of remote-thread interruption.* There are no more Wasmtime traps that produces the `Interrupted` trap  code, although we may wish to move future traps to this so I left it  in place.* The C API support for interrupt handles was also removed and bindings  for epoch methods were added.* Function-entry checks for interruption are a tiny bit less efficient  since one check is performed for the stack limit and a second is  performed for the epoch as opposed to the `Config::interruptable`  style of bundling the stack limit and the interrupt check in one. It&apos;s  expected though that this is likely to not really be measurable.* The old `VMInterrupts` structure is renamed to `VMRuntimeLimits`.

            List of files:
            /wasmtime-44.0.1/crates/c-api/include/wasmtime/engine.h</description>
        <pubDate>Mon, 14 Mar 2022 20:25:11 +0000</pubDate>
        <dc:creator>Alex Crichton &lt;alex@alexcrichton.com&gt;</dc:creator>
    </item>
</channel>
</rss>
