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.
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.
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.