JosephFerano/flan
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

The measurements the handoff was missing: the baseline held exactly

Browse Source
This commit is contained in:
Joseph Ferano 2026-09-13 22:49:19 +07:00
parent 5442c11389
commit dc2b5ed02a
1 changed files with 12 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
HANDOFF-x86-redef.md
View File

@ -99,16 +99,18 @@ That is `C-c C-c` on an existing `defn`, which is the demo, and it is what `test
Also still true and still worth doing: **run `spike/x86/survey.sh` in CI**.
## After
## After, measured
`spike/x86/cells.sh`: **4/4 ok**, run after every change here.
| | before (`b1cc67b`) | after |
|---|---|---|
| `spike/x86/survey.sh` | 97 MATCH / 0 DIFFER / 0 refused | **97 / 0 / 0**, skips `28 does-not-compile / 6 no-main / 2 runs-forever` — identical |
| `spike/x86/cells.sh` | 4/4 ok | **4/4 ok** |
| `dune test --root .` | exit 0 | **exit 0**, run without a pipe |
`spike/x86/survey.sh` and `dune test --root .`: **re-run both and fill these in.** They were still running when
this file was committed and an unmeasured claim is worth less than an admitted gap. Run `dune test --root .`
**without a pipe** — piping to `tail` gives you `tail`'s exit status, which is the trap this file already warns
about two sections up, and the `dev-robust` fixture puts `ld` and `clang` failure text in the output either way.
The skip breakdown is the line that matters beyond the MATCH count, because the no-`main` relaxation is the one
change here not gated behind `ext` being false. It cannot in fact move it: `survey.sh:70` classifies `no-main`
off the **LLVM** build failing at the link, before it ever runs the x86 one.
One thing to look at in the survey beyond the MATCH count: the skip breakdown must still be
`28 does-not-compile / 6 no-main / 2 runs-forever`. The no-`main` relaxation above is the only change here that
is not gated behind `ext` being false, so it is the only one that can move a whole-program result, and a
no-`main` program that now compiles and fails at the link would show up there rather than in MATCH.
And run `dune test --root .` **without a pipe**: piping to `tail` gives you `tail`'s exit status, which is the
trap this file warns about at the top, and the `dev-robust` fixture puts `ld` and `clang` failure text in the
output either way.