Measure Wado's performance or the size of the Wasm it generates, and refresh the benchmark/ and wasm-size/ README files. Use for any benchmarking or size-measurement request, whichever benchmark it names.
中文简介正在准备中。当前显示原文说明。
Run binaryen's wasm-opt over the core Wasm that Wado generates, and read what it changes. Use for any question about wasm-opt or binaryen, or to find where Wado's codegen leaves size or speed on the table.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
wasm-opt reads a core module, not a component. jco splits a Wado component and hands back its core module, so the pipeline runs through jco. What wasm-opt then removes shows what Wado's own codegen could remove.
binaryen is not in the mise registry, and mise's github: backend gets a 403
from the GitHub API in a cloud session. Download the release tarball instead:
curl -sSL https://github.com/WebAssembly/binaryen/releases/download/version_133/binaryen-version_133-x86_64-linux.tar.gz | tar xz -C scratchpad
wasm-tools comes from mise. Where its shim reports no version set, call the
binary under ~/.local/share/mise/installs/wasm-tools/latest/ directly.
B=scratchpad/binaryen-version_133/bin
S=scratchpad/wasm-opt
FEATURES=(--mvp-features --enable-sign-ext --enable-mutable-globals
--enable-nontrapping-float-to-int --enable-simd --enable-relaxed-simd
--enable-bulk-memory --enable-bulk-memory-opt --enable-call-indirect-overlong
--enable-exception-handling --enable-tail-call --enable-reference-types
--enable-multivalue --enable-gc --enable-extended-const --enable-multimemory)
mkdir -p $S
wado compile -Os -f no-wide-arithmetic prog.wado -o $S/prog.wasm
node scripts/jco/transpile-released.mjs $S/prog.wasm $S/jco # → $S/jco/prog.core.wasm
$B/wasm-opt "${FEATURES[@]}" $S/jco/prog.core.wasm -o $S/none.wasm
$B/wasm-opt "${FEATURES[@]}" -O3 $S/jco/prog.core.wasm -o $S/O3.wasm
-Os the baseline. It is -O2 with the name section stripped and
assert messages dropped. An -O2 baseline counts about 9KB of names that
wasm-opt drops by default.-f no-wide-arithmetic is required, since the module is run on V8 (see the
jco skill).-all: it lets wasm-opt emit proposals V8 cannot load,
compact imports among them.none.wasm) re-encodes the module and nothing more,
so it separates encoding waste from optimization.-g to keep function names for a diff. Measure size without it.wasm-tools objdump gives the size and count of each section.wasm-tools dump annotates every byte. Use it for encoding questions, such
as how the local declarations are grouped.wasm-tools print gives WAT to diff. A whole-module diff is too large to
read, so compare per-function instruction counts and opcode histograms with a
small Node script instead.-O2 --skip-pass=NAME measures what one pass is worth: the bytes -O2 grows
by without it. Passes overlap, so these do not add up to the whole gap.
Running a pass alone misleads for the -optimizing variants, which rerun the
whole function pipeline on what they touch.To run the result, copy the jco output directory and replace its
<name>.core.wasm. Then run it as the jco skill describes. Keep a median of
at least 7 runs per variant, since the spread on a cloud VM is ±15%.
Sizes of the zlib benchmark's core module:
| Variant | Bytes |
|---|---|
Wado -Os | 76,476 |
| wasm-opt, no pass | 76,943 |
wasm-opt -O2 | 70,073 |
wasm-opt -O3 | 67,979 |
wasm-opt -Oz | 67,853 |
Re-encoding alone makes this module 467 bytes larger, so binaryen's encoding finds nothing to save in Wado's.
In 2026-09, on Node 26, decompression ran faster under wasm-opt -O2 and
-Os: the median rose 10–40% across two sessions. Compression, and everything
under -O3, stayed within the noise.
What each -O2 pass is worth, by --skip-pass:
| Pass | Bytes | What it does to Wado's output |
|---|---|---|
coalesce-locals | 2,230 | Mostly cleans up after inlining: 337 run alone |
inlining-optimizing | 1,799 | Takes 114 functions to 53 |
optimize-instructions | 1,164 | Peepholes, ref.as_non_null among them |
remove-unused-brs | 1,062 | Turns block/br_if/return into if/else |
precompute-propagate | 782 | Constant propagation |
dae-optimizing | 758 | Drops unused and always-constant parameters |
heap2local | 664 | Turns non-escaping structs into locals |
vacuum, merge-blocks | 824 | Removes the blocks the passes above leave behind |
What wasm-opt removes, as open codegen targets:
wir_optimize/local_layout.rs groups them, and puts the most used first.-O2 keeps 69. Most of the
rest go with the functions it inlines.ref.as_non_null: -O2 takes the count from 388 to 16. Codegen added
most of them, after reads of nullable global slots. A global promoted to a
non-null constant now has a non-null slot
(wir_optimize/const_global.rs). The object of a GC access, which traps on
null by itself, is not narrowed (wir_optimize/cleanup.rs). The -Os build
keeps 17.local.set X followed at once by local.get X occurred
1,191 times. wasm-opt turns it into a local.tee or removes it. The last WIR
pass fuses each pair into a tee (fuse_remaining_local_tees), and copy
propagation removes a copy of a tee'd local. The -Os build keeps 39 pairs.simplify-locals moves a local.set into the one read of
it, so the value stays on the stack. -O2 removes 565 local.set and 725
local.get, and adds 188 local.tee.wir_optimize/local_coalesce.rs does the
same per Wasm type. On the -Os build it takes 2,752 locals to 1,020.-O2 takes block from 229 to 57, br_if from 191
to 54, and return from 184 to 44, while if grows from 1,278 to 1,385.-O2 inlines functions with one caller whatever
their size, inflate_fast among them.-Os build has none. The -O2 build keeps 9
copies of the outlined $cold0 bounds-check path of List<T>::index_value
and index_assign, one per element type, and i32's Display::fmt equals
its Inspect::inspect. --duplicate-function-elimination saves 4,722 bytes
there. Two param_spec clones whose bindings differ can fold to one body
(fmt_float_special$spec0 and $spec1 in json_twitter).$initialize_module. wir_optimize/empty_work.rs removes the calls
to it and the once-flag that guarded them, and DCE drops both.还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Measure Wado's performance or the size of the Wasm it generates, and refresh the benchmark/ and wasm-size/ README files. Use for any benchmarking or size-measurement request, whichever benchmark it names.
中文简介正在准备中。当前显示原文说明。
Measure how long GitHub Actions jobs and steps took across past runs, and find the pull request that made CI slower. Use for any question about CI duration, a slow job, or when CI got slow.
中文简介正在准备中。当前显示原文说明。
How to answer code review feedback — a human reviewer, CodeRabbit, or any review bot. Verify the findings, report the classes they are instances of to the user before fixing, then fix the class rather than the sites named. Put design decisions to the user, then run /distill. Invoke when responding to review comments on a pull request, or to the findings of a /code-review run.
中文简介正在准备中。当前显示原文说明。
Investigate and improve code coverage for the wado-compiler crate. Use for any question about what the tests do and do not reach, dead code included.
中文简介正在准备中。当前显示原文说明。
Review the branch with /code-review at high, then answer the findings with /code-review-response.
中文简介正在准备中。当前显示原文说明。
Use rust-gdb to inspect variables and step through code without modifying it. Prefer it over print debugging for any investigation into what the compiler is actually doing (lldb is unavailable on Claude Code Web).
中文简介正在准备中。当前显示原文说明。