diff options
| author |  zinc <zinc@downsta.ir>
| 2026-10-14 09:44:36 +0000 |
|---|---|---|
| committer | zinc <zinc@downsta.ir>
| 2026-10-14 09:44:36 +0000 |
| commit | 6da86b1e45113c708f54bf28500eeb90365439b2 (patch) | |
| tree | 6a6e686eeea4ceb65e632124e38819331a8fa1b9 /README.md | |
| parent | todo: compiler file split, cross-reference report, local records, x86-64 jit (diff) | |
| parent | parity: compare what zc0 and the self-hosted compiler print (diff) | |
Merge branch 'worktree-agent-aaf6bc066598a6622' into ccr-0054c02e-dfdvnd
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -31,13 +31,14 @@ run these commands from the repository root. everything built or generated goes make build/bin/zy < examples/hello.zc make test JOBS=4 +make parity make genome make web make js make run PROG=examples/hello.zc ``` -the cores embed their genome with c23 `#embed`, so the c compiler has to be clang 19 or gcc 15 or later. `src/tools/findcc.sh` finds one (`CC` set on the command line or in the environment is used as given, and must support it too). `make genome` bootstraps the compiler, compares two self-compiled images, and writes `build/core/genome.bin` only after they agree; `make` reruns it whenever a source of the genome changes, and the cores that embed it are rebuilt after it. `make check` runs the smaller suite while iterating. `ONBOARD.md` is a reading and verification order for getting to know the code. +the cores embed their genome with c23 `#embed`, so the c compiler has to be clang 19 or gcc 15 or later. `src/tools/findcc.sh` finds one (`CC` set on the command line or in the environment is used as given, and must support it too). `make genome` bootstraps the compiler, compares two self-compiled images, and writes `build/core/genome.bin` only after they agree; `make` reruns it whenever a source of the genome changes, and the cores that embed it are rebuilt after it. `make check` runs the smaller suite while iterating. `make parity` (`src/tools/parity.sh`, `--help` for options) compiles the test and example programs with zc0 and with the self-hosted compiler and compares what they print, which the fixpoint check cannot see; programs zc0 rejects are skipped and counted, intended differences are listed in `tests/parity.known`, and work files go to `build/parity/`. `ONBOARD.md` is a reading and verification order for getting to know the code. ### command-line help |