镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

ABI: implement the pinned Home private-JSC profile #163

Closed

Description

@chrisbbreuer

Parent: #140
Public Home embedding compatibility remains separate under #162.

The private compatibility target is Home 7ed99c02e50034f869d0db6d487115bb44332fe4. Its generated inventory pins every declaration, provider, layout, calling convention, and semantic contract; mismatched revisions and drift fail explicitly.

Acceptance

  • Pin the exact Home revision and private binding source set.
  • Inventory every required private symbol, layout, calling convention, and semantic assumption.
  • Implement the complete declared profile behind the private shim boundary.
  • Reject unknown or mismatched profile revisions.
  • Add generated verification and independently compiled consumer fixtures.
  • Reach zero missing and zero unclassified entries.

Terminal evidence

Activity

  1. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    #253 complete: Home 260/431 with 171 pending; compiled consumer 259/259; zero unclassified.

  2. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    #255 adds both Home-profile contiguous-vector exports and focused runtime evidence. Progress is now 262/431 implemented, 169 pending, with the compiled fixture at 261/261 and zero unclassified declarations. #254 is linked as open work.

  3. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    #254 adds the Home-profile async stack export and runtime metadata. Home is now 263/431 implemented with 168 pending; the compiled fixture is 262/262 and the Home audit remains zero-unclassified.

  4. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    Opened #256 for the next bounded private-ABI slice: validated MAP_PRIVATE shared-memfd import into exact ArrayBuffer/Uint8Array values with no-copy slice semantics and exactly-once full-region unmapping. Opaque native JSC::ArrayBuffer handles remain deliberately separate until their producer/lifetime contract is specified.

  5. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    Completed #256 on main through ae61fd67 (runtime e0164ae9). Evidence: focused ownership/GC matrix green; compiled consumer 263/263; Home 264/431 with 167 pending; Bun 258/421 with 163 pending; both audits zero-unclassified; Bun-selected tags green. README/docs are current, while the 1,540-sample benchmark remains unchanged because this embedding-only path is outside the workload.

  6. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    Opened #257 for the three opaque native ArrayBuffer exports plus their real bindgen producer. The pinned converter transfers RefPtr<JSC::ArrayBuffer>::leakRef() as an adopted +1, so completion requires an independent backing-store handle that can outlive its JS wrapper/VM—not a raw cell pointer or realm-retaining test adapter.

  7. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    Opened #258 for the next executable private-ABI cluster: exact GetterSetter/CustomGetterSetter cells, their four null predicates, generated type checks, and non-indexed property traversal that returns descriptor cells without invoking ordinary getters.

  8. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    Opened #295 for the next bounded private-ABI slice: the two pinned SystemError__* error-construction exports (SystemError.zig, pending in both inventories). Taking this track in parallel with the in-flight WebAssembly work, which stays with the other agent.

  9. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    #295 complete: both pinned SystemError__* bridges are on main through 8874cb1e (docs 26003992). Home is now 278/431 implemented with 153 pending; the compiled consumer is 280/280 and both audits remain zero-unclassified. The pre-existing gc.test slab-layout failure noted in the issue evidence belongs to the in-flight GC/WASM work on main, not this slice.

  10. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    #301 complete: the pinned JSC__JSGlobalObject__bunVM owning-VM query is on main through 731e218f (docs 95bc0ceb). Home is now 279/431 implemented with 152 pending; the compiled consumer is 281/281 and both audits remain zero-unclassified.

  11. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    Claiming next slice (non-wasm track): VM execution-control exports — JSC__VM__getAPILock / holdAPILock / releaseAPILock / setExecutionTimeLimit / clearExecutionTimeLimit / hasExecutionTimeLimit (VM.zig, pending in both inventories). Child issue: #302.

    Deferred from this cluster with rationale (will note in the inventory docs on landing):

    • JSC__VM__create / JSC__VM__deinit / JSC__VM__deferGC — create/deferGC have no definition anywhere in Bun's C++/Zig tree (consumer-side externs only; deferGC needs GC deferral machinery), and Bun's deinit is an empty function — a bare-VM-without-global model doesn't map onto zig-js context groups without deeper design work.
    • Zig__GlobalObject__create / createForTestIsolation / destructOnExit — full WebCore global construction (console client, worker env, napi-env adoption, gcProtect roots); engine-feature depth, not an ABI slice.
  12. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    #302 landed and closed: VM execution-control exports (6 symbols).

    • Commits: 7f6cbf17 feat(abi) + e1b0755f docs(abi), pushed to main
    • Fixture: 287/287 symbols linked; runtime matrix passed — including a real 30 ms watchdog interruption of while (true) {} attributed via termination_requested, and a cross-thread API-lock exclusion proof
    • Inventories: Home 285/431 implemented (146 pending), Bun 277/421 (144 pending) — exactly six status flips each; zero unclassified
    • Audits: bun-private-abi-audit, c-api-audit (117/117, 293 private profile exports), test-home-public-abi (50/50), test-c-api, -Dtest-filter=c_api (148/148) all green
    • Full zig build test: validated baseline-vs-candidate on clean-HEAD worktrees pinned to the same base — 1120/1121 both runs, identical single pre-existing gc-slab failure from the in-flight wasm/gc track, zero new failures

    Design notes: API lock = recursive per-CContextGroup mutex (JSLock owner-thread recursion); time limit = lazily spawned host-watchdog thread per group using the documented Context.requestTermination() contract, joined in group destroy; timeout mapping mirrors JSC::Watchdog (+inf/noTimeLimit, NaN armed-never-fires, saturation); documented platform delta — zig-js treats watchdog termination as terminal for the context. Remaining deferrals from this cluster (JSC__VM__create/deinit/deferGC, Zig__GlobalObject__create*/destructOnExit) recorded in the claim comment above.

  13. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    Claiming next slice: JSGlobalObject__setTimeZone (JSGlobalObject.zig, pending in both inventories) — process-wide default-timezone override with real Intl/Temporal default-zone consumers. Child issue: #303.

    Also noting for the record: Zig__GlobalObject__getModuleRegistryMap / resetModuleRegistryMap are dead code upstream (bindings return nullptr/false with "no callers" — ZigGlobalObject.cpp:834-846); they'll be deferred rather than landed as behavior-free symbols.

  14. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    #303 landed and closed: process default-timezone override (1 symbol, both inventories).

    • Commits: f2bc3d9f feat(abi) + d1abe65a docs(abi), pushed to main
    • Fixture: 288/288 symbols linked; runtime matrix passed — UTC baseline, null tolerance, unknown-zone rejection without state disturbance, canonical acceptance, explicit-option precedence, process-wide visibility from a foreign VM (WTF parity), lowercase normalization, alias canonicalization (America/Atka → America/Adak), empty-string reset
    • Inventories: Home 286/431 implemented (145 pending), Bun 278/421 (143 pending); zero unclassified
    • Audits: bun-private-abi-audit, c-api-audit (117/117, 294 private profile exports), test-home-public-abi (50/50), test-c-api, -Dtest-filter=c_api (148/148) all green
    • Full zig build test: baseline-vs-candidate on clean worktrees pinned to 7be5f42d — 1134/1135 both runs, identical single pre-existing gc-slab failure, zero new failures; temporal/intl filters green

    Implementation: process-wide override in src/interpreter.zig (setTimeZoneOverride/timeZoneOverride/validCanonicalTimeZoneName sharing the Intl pipeline's case normalization + alias + canonical-IANA check), consumed by the Intl.DateTimeFormat default zone and Temporal.Now default zone/timeZoneId(); export in src/c_api.zig. Documented boundary: Date local-time methods stay UTC-coincident by engine design; pinned date-cache reset is vacuous (no cache).

  15. chrisbbreuer commented on Jul 18, 2026

    @chrisbbreuer
    MemberAuthor

    Claiming the next slice: VM trap notifications → child issue #304.

    • JSC__VM__notifyNeedWatchdogCheck (VM.zig:142) — implement: VM-wide trap flag consumed at the interpreter's step checkpoint, re-checking the armed Private ABI: VM execution-control exports (API lock + execution-time-limit) #302 execution deadline on the executing thread.
    • JSC__VM__notifyNeedDebuggerBreak (VM.zig:148) — implement: requests an inspector pause (reason "pause") at the next statement boundary on every realm of the VM with an enabled debugger session; inert without one, matching JSC.
    • JSC__VM__notifyNeedShellTimeoutCheck (VM.zig:154) — rejected: jsc-shell --timeout-specific trap, no possible zig-js consumer (same category as SourceProvider__deref). Recorded in Private ABI: VM trap notifications — watchdog check + debugger break #304 and will be reflected in the next body sync.
  16. 37 remaining items

  17. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    #393 core advances the pinned Home private profile to 410/471 implemented (61 pending) in 18527d73; Debug/ReleaseSafe consumer evidence passes. #394 remains linked for the falsy-constructor inspector fallback.

  18. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    Profile update: #393 and #394 are complete through 522e19c. The Home private ABI remains 410/471 implemented with 61 explicitly pending; received-value diagnostics now have compiled consumer, source-contract, Debug, and ReleaseSafe evidence.

  19. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    #396 implements eight shared Home imports and refreshes the exact inventory from 410 to 418 implemented private symbols, leaving 53/471 pending. The Home profile library compiles/links/runs the external inspector-agent consumer in Debug and ReleaseSafe. CI evidence is pending in run 29766523096.

  20. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    #398 moves five shared HTTPServer inspector imports to implemented. Home is now 423/471 implemented, 48 pending with exact contract/source hashes and the shared external consumer passing Debug and ReleaseSafe. Fixing main CI: https://github.com/zig-utils/zig-js/actions/runs/29769670857

  21. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    #400 moves Bun__onSignalForJS to implemented. Home is now 424/471 implemented, 47 pending; exact contract plus Debug/ReleaseSafe external consumer evidence pass.

  22. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    #396, #398, and #400 are closed on green bounded CI. The currently published Home profile is 424/471 (47 pending); #401 is implemented and locally verified to move it to 425/471 (46 pending), pending its isolated push.

  23. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    Published Home profile checkpoint 737bd957: 427/471 private symbols implemented, 44 pending. #401 contributes the Home-only execution-context retirement boundary; #402 contributes two shared exact module-registry shims.

  24. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    New tracked child #404 owns the remaining CPU sampling-profiler ABI cluster: per-VM lifecycle, safe cooperative stack sampling, Chrome/Markdown serialization, Home/Bun output ownership, OOM, and sanitizer evidence. This keeps the three profiler symbols out of the broad pending bucket without treating link-only stubs as progress.

  25. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    The three CPU profiler exports are implemented by #404 on main through 9ab79698. Home inventory is now 433/471 (38 pending); Debug, ReleaseSafe, and TSan cross-profile fixtures are green locally.

  26. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    Next Home pending cluster is tracked in #405: six readable-stream conversion exports and their required stream state machine.

  27. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    #404 is complete. Per-VM CPU sampling profiles landed through 9ab796987fe04331761e620b2e928b9534330a4f; the exact fixing-main private-abi-boundary job passed its Debug, ReleaseSafe, and TSan evidence. The pinned counts remain Home 433/471 and Bun 424/461 at that checkpoint; #405 is the next active private-ABI slice.

  28. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    #405 is implemented on main through 4275f7c2: all six pinned ReadableStream consumers now share realm-local stream/reader/controller machinery, exact Home/Bun contracts, and compiled Debug/ReleaseSafe/TSan fixtures. Inventories are now Home 439/471 (32 pending) and Bun 430/461 (31 pending). #405 remains open only for its exact fixing-main CI gate.

  29. chrisbbreuer commented on Jul 20, 2026

    @chrisbbreuer
    MemberAuthor

    Created #406 for the next coherent boundary: real WebAssembly.compileStreaming/instantiateStreaming plus the pinned JSC__Wasm__StreamingCompiler__addBytes opaque feed. It explicitly preserves the frozen WG1 baseline while validating modern coverage through the existing WG3 and upstream-main profiles.

  30. chrisbbreuer commented on Jul 21, 2026

    @chrisbbreuer
    MemberAuthor

    The declared exact profile is complete with zero pending/unclassified entries, and exact main e3fdc52385204c75fe6ae5c64d48dae6e5ede418 passed all 43 jobs in run 29806223245.

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