History log of /wasmtime-44.0.1/docs/examples-pulley.md (Results 1 – 5 of 5)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7, v43.0.0, v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3, v41.0.2, v41.0.1, v36.0.5, v40.0.3, v41.0.0, v36.0.4, v39.0.2, v40.0.2, v40.0.1, v40.0.0, v39.0.1, v39.0.0, v38.0.4, v37.0.3, v36.0.3, v24.0.5, v38.0.3, v38.0.2, v38.0.1, v37.0.2, v37.0.1, v37.0.0, v36.0.2, v36.0.1, v36.0.0, v35.0.0, v24.0.4, v33.0.2, v34.0.2, v34.0.1, v33.0.1, v24.0.3, v32.0.1, v34.0.0, v33.0.0
# eed7c104 05-May-2025 Alex Crichton <[email protected]>

pulley: Allow disabling SIMD in the interpreter at compile-time (#10727)

This commit adds a new feature to Pulley which is used to reduce the
compiled code size of the interpreter itself by disablin

pulley: Allow disabling SIMD in the interpreter at compile-time (#10727)

This commit adds a new feature to Pulley which is used to reduce the
compiled code size of the interpreter itself by disabling SIMD opcode
interpretation at compile-time. The goal here is to be low-impact on
Pulley itself to avoid needing `#[cfg]` all over the place and to
additionally avoid the need to redesign Pulley's opcode macro for use in
various parts of Wasmtime.

Methods are annotated with a custom macro in the interpreter which
registers a `#[cfg]` that either does the listed implementation or
switches to an implementation that emits a trap if executed. This means
that it's safe to execute mismatched code where SIMD was enabled at
compile time but disabled at runtime, it just means the semantics may be
a 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. Cargo
features aren't a great fit for this sort of feature so an explicit flag
is used.

show more ...


# 92cfda1b 02-May-2025 Victor Adossi <[email protected]>

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 ap

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 <[email protected]>

show more ...


# 54988feb 22-Apr-2025 Nick Fitzgerald <[email protected]>

Add a bunch of cookbook-style "how do I do X?" examples to the book (#10630)

This tries to cover things that we repeatedly get questions about on Zulip.


Revision tags: v32.0.0
# 3e406d2e 20-Mar-2025 Alex Crichton <[email protected]>

Add a `wasmtime objdump` subcommand (#10405)

This commit adds an `objdump` subcommand to the `wasmtime` CLI. Like all
other subcommands this can be disabled for a more minimal build of the
CLI as we

Add a `wasmtime objdump` subcommand (#10405)

This commit adds an `objdump` subcommand to the `wasmtime` CLI. Like all
other subcommands this can be disabled for a more minimal build of the
CLI as well. The purpose of this subcommand is to provide a
Wasmtime-specific spin on the venerable native `objdump` itself. Notably
this brings Wasmtime-specific knowledge for filtering functions, showing
Wasmtime metadata, etc.

This command is intended to look like `objdump` roughly but also has
configurable output with various flags and things that can be printed.
For now the main Wasmtime additions are showing the address map
section, stack map section, and trap section of a `*.cwasm` file.

This new subcommand replaces the infrastructure of the `disas` test
suite, and now that test suite uses `wasmtime objdump` to generate test
expectations. Additionally the subcommand replaces the Pulley `objdump`
example as a more full-featured objdump that also works natively with
Pulley.

The hope is that if we add more binary metadata in the future (such as
unwinding tables) that can be relatively easily added here for
exploration as well. Otherwise this is mostly just a developer
convenience for Wasmtime developers as well and hopefully doesn't cost
too much in maintenance burden.

Closes #10336

show more ...


Revision tags: v31.0.0, v30.0.2, v30.0.1, v30.0.0
# 8a969897 23-Jan-2025 Alex Crichton <[email protected]>

Add book-level documentation for Pulley (#10095)

* Add book-level documentation for Pulley

This commit adds some longer form documentation about Pulley in
Wasmtime's online documentation book. This

Add book-level documentation for Pulley (#10095)

* Add book-level documentation for Pulley

This commit adds some longer form documentation about Pulley in
Wasmtime'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.md

Co-authored-by: Joel Dice <[email protected]>

* Don't test examples

---------

Co-authored-by: Joel Dice <[email protected]>

show more ...