chore: syncing of wasm-exts to provide new instructions (e.g. SIMD!)#6043
Draft
chore: syncing of wasm-exts to provide new instructions (e.g. SIMD!)#6043
wasm-exts to provide new instructions (e.g. SIMD!)#6043Conversation
Contributor
ggreif
changed the title
wasm-exts to provide new instructions (e.g. SIMD!)wasm-exts to provide new instructions (e.g. SIMD!)
ggreif
added a commit
that referenced
this pull request
Apr 22, 2026
Moved to PR #6043 (wasm-exts sync), which will be the natural home for constant-tracking reasoning as new instructions come in. No content loss — the file is reproduced verbatim on gabor/wasm-exts-sync. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Moves the plan file here from PR #5961's branch where it sat as a leftover companion doc. Outlines the forthcoming `wasm-exts` sync work — pulling upstream instruction support forward so codegen can emit SIMD, newer ref-types, etc. This PR is the natural home. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
ggreif
force-pushed
the
gabor/wasm-exts-sync
branch
from
c3b35dc to
35f58d0
Compare
ggreif
added a commit
that referenced
this pull request
Apr 22, 2026
Moved to PR #6043 (wasm-exts sync), which is the natural home for the upcoming instruction-catchup work. No content loss — file is reproduced verbatim on gabor/wasm-exts-sync. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tracking branch for syncing the vendored
wasm-extslibrary with upstream to pick up newer Wasm instruction support — SIMD being the most immediate carrot, but also EOP32/EOP64 refinements, table refs, etc.Motivation
Motoko's
wasm-extsfork lags the upstreamreference-types/simd/relaxed-simdwork. Pulling it forward unlocks:Scope
Starting empty — this PR just carries the
abstract-interpreter.mdplan doc moved over from PR #5961's branch, since the sync work will want to reason about how constant-tracking survives the new opcodes. Actualwasm-extsbumps and codegen plumbing land in follow-up commits.Related
.claude/plans/abstract-interpreter.md— background on the ConstTrack abstract interpreter (relevant for reasoning about any new instructions we start emitting).fmodfet al.libmcalls) and zero-forwarders (Motoko-specific) #5961 — where this plan doc originated; will be dropped there in a follow-up commit.🤖 Generated with Claude Code