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
The production age-three nursery currently reclaims and promotes without relocating surviving young cells. The README removal gate requires a moving nursery whose copying/promotion path reuses the exact relocation contract and remains safe during mid-script no-GIL minor collection.
Acceptance
Copy surviving young cells between age spaces and promote terminal-age survivors with stable IDs and failure-atomic forwarding metadata.
Rewrite precise roots, old-to-young remembered edges, young-to-young edges, weak/finalization state, handles, interpreter/baseline/optimizer stack maps, and embedding roots during every moving minor cycle.
Preserve persistent-card correctness and eliminate stale from-space pointers before mutators resume; verify the full relocation inventory after each stress cycle.
Coordinate bounded parallel mid-script minor rendezvous across shared-realm mutators without a context GIL, including allocation failure and collector abort recovery.
Keep conservative stacks and opaque native frames explicitly pinned or fail closed; never infer interior/base pointers from untyped words.
Publish exact-parent pause, throughput, bytes-copied, promotion, retained-backing, and timeout evidence; update the release matrix and README only from committed artifacts.
Implementation landed on main in 56dfc7d6 (feat(gc): move multi-age nursery survivors) with the reusable collector layer in zig-utils/zig-gc@958563a (feat(heap): move multi-age nursery survivors).
Completed mechanics:
Every live young survivor moves after minor weak/sweep processing, including terminal-age promotion, while preserving process-stable cell IDs.
Destination and forwarding planning are failure-atomic; OOM leaves roots/edges/addresses unchanged and increments movement-failure telemetry.
Exact Context, interpreter/VM, baseline/optimizer stack-map, protected Zig, C-API, private strong/weak, remembered, young-to-young, weak/ephemeron/finalization, and Wasm/embedding dispatch all reuse the verified relocation inventory.
Promotion creates a persistent old-owner card so a parent that ages ahead of its child remains a valid frontier across later moving minors.
Shared no-GIL movement uses the existing bounded 100 ms exact-generation rendezvous. Opaque peers time out without consuming work; a deterministic retry test proves the same request later completes.
JIT-enabled shared allocation pressure now publishes a distinct moving-checkpoint wake word. Exact native checkpoints move; opaque paths get a four-tranche bounded opportunity before conservative non-moving fallback.
The final two checklist items intentionally remain open until the exact-parent generation benchmark publishes pause/throughput/bytes-copied/promotion/retained-backing/timeout evidence from a clean commit. Related automatic-stop evidence remains tracked in #446.
Closure evidence landed in e1a51b0b and release-inventory follow-up 8f7ea6e0.
The committed July 29 matrix contains 112 exact moving/non-moving age-one/age-three rows, zero movement failures, nonzero copy telemetry for survivor workloads, a three-mutator no-GIL parent, bounded retries, raw TSV, and a generated report. Moving age-three measured 0.63–1.01x its exact non-moving parents; 480.42 MiB was copied across the recorded moving age-three rows. Full units were 1,458/1,458, focused moving-nursery coverage passed in Debug/ReleaseSafe/TSan, and the release inventory now marks generational_gc green (11/12 overall).
Related #446 owns the remaining automatic-compaction coverage audit; it no longer blocks the moving multi-age nursery itself.
Activity
feat(heap): move multi-age nursery survivors
feat(gc): move multi-age nursery survivors
chrisbbreuer commentedon Jul 29, 2026
Implementation landed on
mainin56dfc7d6(feat(gc): move multi-age nursery survivors) with the reusable collector layer inzig-utils/zig-gc@958563a(feat(heap): move multi-age nursery survivors).Completed mechanics:
Verification on the pushed source:
zig build test-parallel: 1,458/1,458 passed, 0 leaked, 10 shards.zig-gc: 56/56 tests.The final two checklist items intentionally remain open until the exact-parent generation benchmark publishes pause/throughput/bytes-copied/promotion/retained-backing/timeout evidence from a clean commit. Related automatic-stop evidence remains tracked in #446.
tools(gc): define moving nursery evidence matrix
fix(gc): isolate forced nursery evidence
fix(gc): stabilize shared nursery samples
docs(release): advance moving nursery gate
chrisbbreuer commentedon Jul 29, 2026
Closure evidence landed in
e1a51b0band release-inventory follow-up8f7ea6e0.The committed July 29 matrix contains 112 exact moving/non-moving age-one/age-three rows, zero movement failures, nonzero copy telemetry for survivor workloads, a three-mutator no-GIL parent, bounded retries, raw TSV, and a generated report. Moving age-three measured 0.63–1.01x its exact non-moving parents; 480.42 MiB was copied across the recorded moving age-three rows. Full units were 1,458/1,458, focused moving-nursery coverage passed in Debug/ReleaseSafe/TSan, and the release inventory now marks
generational_gcgreen (11/12 overall).Related #446 owns the remaining automatic-compaction coverage audit; it no longer blocks the moving multi-age nursery itself.
fix(gc): report concurrent compaction conflicts
docs(release): complete compatibility matrix