release
The self-hosted compiler is now the release compiler
Sessions 31-34 crossed the line that turns self-hosting from a party trick into the product: the compiler you download is the compiler written in Fid.
What shipped
fid.exeis the release binary. The Windows installer now ships the self-hosted compiler (release/fid.exe, built byRELEASE=1 ./scripts/bootstrap.sh) with the Rust bootstrap compiler beside it asfidesc.exe. v1.0.0’sfides.exename is retired.- Release bootstrap with fixpoint check: three stages, stage 2 == stage 3 verified byte-for-byte (~38 MB of C) on every release build, then the compiler is installed and smoke-tested from an installed layout.
- Test parity:
fid runmatchesfidescon all 302 test programs and all 10 examples;fid ccompileon 242/243 (test_sqliteneeds libsqlite3; the Rust compiler fails it the same way); all expected-fail tests rejected. - A Fides runtime for the PE backend:
stdlib/pe_runtime/(thep_X→pert_X/pe_*builtins merged into everyemit) means native Windows executables now run the entire test suite (threads, channels,select, async, tensors, JSON, files) with no C compiler anywhere in the loop. - Reproducible and incremental builds: an artifact store keyed on content hashes kills stale-binary bugs;
fid ccompile --incbuilds one translation unit per module and caches the objects.
Fixes that made parity possible
@conserve now actually rejects non-conserving calls (it used to only check effects), second impl blocks in imported modules are kept, extern "C" link "lib" libraries are linked on the C path, and tests that printed timings or random values were made deterministic so the suites can be compared byte-for-byte.