v4: init.4th and the ACL at call; the F18 ADR, ABI and artifact layout; ADR step 3 tasks 1-3 (mkf18a) #198

Merged
rajames merged 52 commits from StarForth-v4.0.0 into master 2026-11-20 18:42:33 +00:00
Showing only changes of commit b5e85392c1 - Show all commits
@@ -30,9 +30,9 @@ existing build system". It builds on:
A C tool beside `mkrom.c`, built the same way, one per cell width:
mkf18a OUT.f18a MAP.f18 SOURCE.f18...
mkf18a OUT.f18a MAP.f18 DIR
1. It assembles the sources with `text.c`, at origin 0, in the order given.
1. It assembles every `.f18` in DIR with `text.c`, at origin 0, in name order (ruled §6.3), after MAP.
2. It writes the artifact, laid out as `ARTIFACT.md` gives:
- the header;
- the provenance, with its four SHA-512 hashes;
@@ -111,7 +111,9 @@ ADR step 8 asks. The boot gains nothing.
artifacts. The nucleus is checked as the tool's assembly against the ROM's, and no artifact file is
written for it. `ABI.md` §4 stands.
Is the nucleus the first artifact, or is a small relocatable train written first?
3. **The order of the sources.** Captain Bob's image is "the .f18 assembler assembles all .f18 files it
3. ~~The order of the sources~~ **Ruled 2026-11-19: "All it finds, name order".** The tool takes every
`.f18` in a train's directory, sorted by name, so the file names set the order (`00-core.f18`, ...) and
there is no list to keep. As asked: Captain Bob's image is "the .f18 assembler assembles all .f18 files it
finds", but the order matters: the map first, `sys_files.h`'s list, `end.f18` last. Does each train
name its order in a list, as `sys_files.h` does, or does the tool take the files in name order?
4. **Which words are exports.** The nucleus defines hundreds of words, and some have no fixed effect, which