This commit is contained in:
2026-03-24 13:40:36 +00:00
parent d929f68dd7
commit 6d875784ea
3 changed files with 69 additions and 37 deletions
-37
View File
@@ -1,40 +1,3 @@
# PR-1.6 — Canonical Function Boundaries & `FRAME_SYNC` Placement (Bytecode Layout)
### Briefing
GC and coroutine scheduling rely on deterministic safepoints. The bytecode layout must define canonical function boundaries and `FRAME_SYNC` semantics at the bytecode layer.
### Target
* Enforce canonical function ranges and end labels.
* Ensure `FRAME_SYNC` placement rules are representable and checkable.
### Work items
* Review current layout utilities and make them canonical for:
* Computing function `code_len`.
* Determining valid jump targets (instruction boundaries).
* Determining function end boundary.
* Document `FRAME_SYNC` at the bytecode level:
* What it signals.
* Where it is required (as per updated specs).
* Update disasm to clearly display `FRAME_SYNC`.
### Acceptance checklist
* [ ] Function boundaries are computed via a single canonical routine.
* [ ] `FRAME_SYNC` is clearly represented and documented.
* [ ] Existing verifier/layout tests (if any) are updated.
* [ ] `cargo test` passes.
### Tests
* Add or update unit tests for layout boundary correctness (e.g., end-exclusive semantics).
---
# PR-1.7 — Bytecode Roundtrip Tests (Encode/Decode/Disasm Sanity)
### Briefing