From de3ccabd62bf98a518481271fda1edb987ea601f Mon Sep 17 00:00:00 2001 From: bQUARKz Date: Thu, 19 Feb 2026 12:46:50 +0000 Subject: [PATCH] pr4.3 --- files/TODOs.md | 53 -------------------------------------------------- 1 file changed, 53 deletions(-) diff --git a/files/TODOs.md b/files/TODOs.md index faf29779..6e3b3b9f 100644 --- a/files/TODOs.md +++ b/files/TODOs.md @@ -1,56 +1,3 @@ -# PR-4.3 — Control Flow and Jump Target Verification - -### Briefing - -The verifier must ensure all control flow transfers are valid and do not jump into the middle of instructions or outside function boundaries. - -### Target - -* Validate all jump targets. -* Reject invalid or unsafe control flow. - -### Work items - -* Use canonical layout utilities to identify instruction boundaries. -* Verify: - - * Jump targets land on valid instruction boundaries. - * Targets are within the function range. -* Reject invalid targets with a verifier error. - -### Acceptance checklist - -* [ ] Invalid jump targets are rejected. -* [ ] Valid programs pass verification. -* [ ] No reliance on runtime traps for these cases. -* [ ] `cargo test` passes. - -### Tests - -* Add tests: - - * Jump to middle of instruction → verifier error. - * Jump outside function → verifier error. - * Valid jump → passes. - -### Junie instructions - -**You MAY:** - -* Reuse layout utilities for boundary checks. -* Add verifier error cases. - -**You MUST NOT:** - -* Modify instruction encoding. -* Introduce new trap codes. - -**If unclear:** - -* Ask before defining jump rules. - ---- - # PR-4.4 — Function Boundary and Terminator Verification ### Briefing