plans: task 4 ruling 2a -- the placer splits the code at each export, entry before code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_017RzZgrf7V7Zk2iczBXDRbm
This commit is contained in:
@@ -329,6 +329,14 @@ and placing them on a node are the ADR's steps 4 and 6 (§3).
|
|||||||
the flags with the ACL defaults, the name, the link, the code. It tells the kernel, as `(WORD-DEFINED)`
|
the flags with the ACL defaults, the name, the link, the code. It tells the kernel, as `(WORD-DEFINED)`
|
||||||
does. The test runs the words by name at the console. Asked: entries now, or calls by address and
|
does. The test runs the words by name at the console. Asked: entries now, or calls by address and
|
||||||
entries left to step 6.
|
entries left to step 6.
|
||||||
|
**2a, ruled 2026-11-20: "Split at each export".** An entry is laid right before its code (`dict.f18`:
|
||||||
|
the four cells at xt-4 to xt-1, the code at xt), but the artifact's code is one block with no room
|
||||||
|
between its words (ruling 1). So the placer lays each export's entry, then that export's code, up to
|
||||||
|
the next export's entry offset. Code before the first export goes first, with no entry. Every cell
|
||||||
|
moves by the entries laid before it, so every relocation is mapped through the moved offsets, and
|
||||||
|
each one's reach is checked at its final address. Calls go straight to the code. A word whose code
|
||||||
|
runs on into the next export's, with no `;` or jump between, cannot be split, and the placer refuses
|
||||||
|
it. Asked: that, or the whole block at the base, with an entry after it whose xt cell jumps to the word.
|
||||||
3. **The nucleus's effects: "Tool assembles it".** `mkf18a` is given the nucleus's directory, assembles it
|
3. **The nucleus's effects: "Tool assembles it".** `mkf18a` is given the nucleus's directory, assembles it
|
||||||
with its map, and derives each header's effect by name, as task 2's measurement did. Nothing is
|
with its map, and derives each header's effect by name, as task 2's measurement did. Nothing is
|
||||||
generated in between. Asked: that, or an effects file generated once per build.
|
generated in between. Asked: that, or an effects file generated once per build.
|
||||||
|
|||||||
Reference in New Issue
Block a user