docs(tms34010-sdk): the r5.01 2ine pipeline and gspcl #13

Merged
arti merged 3 commits from opencode.energia.arti.ee/vt1200:docs/r5.01-2ine-pipeline into master 2026-11-17 04:32:37 +02:00
3 Commits
Author SHA1 Message Date
opencode b032347cf0 docs(tms34010-sdk): what gspcl chains, the fork's status note, exit codes
Be precise about the driver: `gspcl` chains compile -> optimize -> codegen ->
assemble; `-z` adds the link, and everything after `-z` is a linker option, so
the libraries follow. That form was measured: `gspcl -k -o2 file.c -z -o
file.out rts.lib flib.lib` exits 0 and leaves file.out.

`3bcdfc3` is the fork's `TMS34010.md` status update, not this document's.

The exit status is an observation from the verified runs, not a loader
contract: `lxTerminate` keeps only the low 8 bits of an OS/2 exit code.

Also record the 2026-11-16 re-verification, bring the OS/2 route's heading and
lead in line with its body, and give that route's CMake command the policy
floor CMake 4.x needs.
2026-11-17 02:31:27 +00:00
opencode fecd0a950d docs(tms34010-sdk): drop the broken-2ine caveats
The docs now describe the working r5.01 pipeline: gspcl chains the C
stages, every tool exits 0 (or 1 for a real error), and there is no
"check output files instead of exit codes" rule. The old 139/SIGSEGV
story stays in git history.
2026-11-17 02:30:20 +00:00
opencode cca0383a79 docs(tms34010-sdk): what the 2ine 139 exit status was
gspac and gspcg returning 139 was a real SIGSEGV, not a strange exit
code: they free their automatic data segment (DGROUP), which also holds
the running 16-bit stack, just before DosExit; lxFreeSegment unmapped it
and the 16->32 bridge faulted returning through it. Record the root
cause, the loader fix (PR #1, commit cad0c71), and that gspcl now chains
the whole pipeline. Keep the "check output files" rule for unpatched
loader builds.
2026-11-17 02:30:20 +00:00