Skip to content

Read memarg flags through a function so the compiler compiles itself - #1530

Merged
ctate merged 1 commit into
mainfrom
ctate/read-memarg-flags-6a056f
Oct 20, 2026
Merged

ctate merged 1 commit into
mainfrom
ctate/read-memarg-flags-6a056f

Conversation

@ctate

@ctate ctate commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator
  • readMemargFlags in the WebAssembly reader takes a () => number instead of a { u32(): number } record, which the self-hosted compiler refused for the validator's and translator's class instances.
  • Fixes the self-hosting LLVM emitter, native frontend program and bootstrap seed jobs on main; WebAssembly validation and translation are unchanged.

readMemargFlags took its reader as a `{ u32(): number }` record, and the
validator (Reader) and translator (WasmCursor) pass class instances. The
self-hosted compiler refuses a class instance in a record-typed parameter
(SC2002), so the self-hosted LLVM emitter, the native frontend programs
and the bootstrap seed builds failed. readMemargFlags now takes the
reader's u32 function, and each caller passes `() => r.u32()`.
@vercel

vercel Bot commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
scriptc Ready Ready Preview, v0 Oct 20, 2026 4:42pm UTC

@ctate
ctate merged commit 0d82842 into main Oct 20, 2026
63 of 65 checks passed
@ctate
ctate deleted the ctate/read-memarg-flags-6a056f branch October 20, 2026 16:48

This branch was successfully deployed

1 active deployment
Preview — 08a3a7cf Deployed Oct 20, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant