Skip to content

WebAssembly Core 3: add an exact wg-3.0 conformance profile #366

Description

@chrisbbreuer

Parent: #142
Related: #268, #300, #147
Roadmap: #134

The checked-out wasm-spec-wg1 submodule intentionally pins stable wg-1.0 for the reproducible MVP corpus. The separate wasm-spec-wg3 submodule pins stable wg-3.0 (9d36019973201a19f9c9ebb0f10828b2fe2374aa). Upstream main remains a moving development target observed for drift, never an unreproducible published score.

Acceptance:

  • Keep the existing wg-1.0 submodule/corpus explicitly labeled as the frozen MVP fixture.
  • Add an exact wg-3.0 profile with a declared feature set and deterministic converter/tool pins.
  • Inventory every Core 3 test command as pass, fail, not applicable (with reason), or runner error; expose zero hidden filtering.
  • Reconcile overlap with the existing Core 2, SIMD, Threads, exceptions, tail-call, multi-memory, Memory64, and GC profiles without double-counting claims.
  • Add bounded exact-pin CI smoke/drift gates plus a deliberate complete-run command.
  • Publish the terminal profile in the machine-readable conformance and release matrices, WebAssembly docs, and the concise README aggregate.
  • Add a non-blocking upstream-main drift report that identifies changes since the stable Core 3 pin without changing the accepted score.

Completion evidence:

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions