Some checks failed
Test, Build, and Deploy / test-build-deploy (push) Failing after 46s
Round 2 conformance fixes: - forth-pic-step: replace float-imprecise body with same two-step 16-bit division as # — fixes #S producing '0' instead of full binary string (GP6/GN1 pictured-output tests) - UM/MOD: rewrite with two-phase 16-bit long division using explicit t - q*div subtraction, avoiding mod_float vs floor-division inconsistency at exact integer boundaries 6 failures remain (SOURCE/>IN tracking and CHAR " with custom delimiter require deeper interpreter plumbing changes). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
29 lines
976 B
Markdown
29 lines
976 B
Markdown
# Forth Hayes Core scoreboard
|
|
|
|
| metric | value |
|
|
| ----------------- | ----: |
|
|
| chunks available | 638 |
|
|
| chunks fed | 638 |
|
|
| total | 638 |
|
|
| pass | 632 |
|
|
| fail | 6 |
|
|
| error | 0 |
|
|
| percent | 99% |
|
|
|
|
- **Source**: `gerryjackson/forth2012-test-suite` `src/core.fr`
|
|
- **Generated**: 2026-05-05T21:30:21Z
|
|
- **Note**: completed
|
|
|
|
A "chunk" is any preprocessed segment ending at a `}T` (every Hayes test
|
|
is one chunk, plus the small declaration blocks between tests).
|
|
The runner catches raised errors at chunk boundaries so one bad chunk
|
|
does not abort the rest. `error` covers chunks that raised; `fail`
|
|
covers tests whose `->` / `}T` comparison mismatched.
|
|
|
|
### Chunk cap
|
|
|
|
`conformance.sh` processes the first `$MAX_CHUNKS` chunks (default
|
|
**638**, i.e. the whole Hayes Core file). Lower the cap temporarily
|
|
while iterating on primitives if a regression re-opens an infinite
|
|
loop in later tests.
|