What the 98 is and is not
This commit is contained in:
parent
c4e68dcc3c
commit
0483ae81e8
@ -163,9 +163,12 @@ NOX86 0
|
||||
SKIP 36
|
||||
```
|
||||
|
||||
That is `HANDOFF-x86-rt.md`'s 97 plus `p9`. It does not include `p10`, whose file did not exist when the run globbed
|
||||
the directory — the targeted run above is `p10`'s row, and the number a later full run should report is **99**. The
|
||||
`SKIP` 36 is the same 28 / 6 / 2 as before.
|
||||
That is `HANDOFF-x86-rt.md`'s 97 plus `p9`, and the `SKIP` 36 is the same 28 / 6 / 2 as before. **Read it as a
|
||||
sanity check and not as the verification of the fix**, for two reasons the honest version has to name: it does not
|
||||
include `p10`, whose file did not exist when the run globbed the directory, and `lib/x86.ml` was rebuilt twice while
|
||||
it was in flight — the `end;` fold and the comment — so some rows were built with the binary before that tidy-up and
|
||||
some after. Both rebuilds were semantically identical, so the counts are not wrong, but they are not one
|
||||
measurement. A clean run of the final binary, which includes `p10`, should report **99 / 0 / 0**.
|
||||
|
||||
The invariant that matters is the two zeroes, and it is worth saying why the item-5 fix cannot have moved anything
|
||||
else: the change removes a refusal and adds no code. A function with `f.unwound` true reaches none of it, and a
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user