You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a6db5dd
Browse filesBrowse the repository at this point in the historyBrowse files
| WIT component marshalling | future | NO | NOT adopted | D-404 |
73
+
| no-max table `table.grow` (JIT) | tier-1 FIXED in v2.0.0 (D-501) — grows to a synth cap `max(min*2, 1024)`; unbounded no-max grow still interp-only | YES (pin) | unaffected (no `table.grow` / table decl in cljw host or FFI fixtures); available if a guest needs it | D-501 |
72
74
73
75
## Forward plan — the JIT adoption unit (gap area II × III) — ACTIVE
74
76
@@ -141,3 +143,11 @@ was the `.auto`-default flip; this ledger tracks adoption status per capability.
141
143
default executes a SIMD body only the JIT can run (`default-simd: 42`), proving the flip.
142
144
Components stay interp-pinned on the zwasm side (D-500), so the component path is unaffected
143
145
and the F-012 diff oracle (explicit `.interp`/`.jit`) is untouched. `to_cljw_09` CONSUMED.
146
+
-**2026-07-01** — **PIN BUMP v2.0.0-alpha.3 → STABLE v2.0.0 (`0853f3c1`)** for the cljw
147
+
1.0.0 release. zwasm cut + published a stable `v2.0.0` GitHub Release (after one failed
148
+
release build + a tag re-cut); it picks up zwasm D-501 tier-1 (no-max table `table.grow`
149
+
under JIT grows to `max(min*2, 1024)`; PR #115) + a test-infra guest-stdout fd guard.
150
+
cljw is behaviorally unaffected (no `table.grow` usage); the full `--serial-e2e` gate
151
+
confirmed the embedding API (`Engine.init` / `runWasmCapturedFull` / `wasi.host.Host` /
152
+
`Module.InstantiateOpts`) is signature-stable. Resolves the D-543 "1.0.0 embeds a
153
+
pre-1.0 zwasm" incoherent-pin story — cljw 1.0.0 now ships on a coherent stable zwasm v2.0.0.
0 commit comments