← board

Restore the ELF-HASH workload to the uforth bench

What

--full is supposed to include the blocktest ELF-HASH section — the known ~100x-slow outlier, and the whole reason the harness tracks a full mode. It currently SKIPs: blocktest.fth needs uforth's block-word preamble (FIRST-TEST-BLOCK, LIMIT-TEST-BLOCK, the [?IF] guards) which tester.fr alone does not provide, so the workload never runs.

Two ways out, either acceptable:

  1. assemble the preamble the workload needs, or
  2. extract the ELF-HASH section as a standalone snippet.

(2) is likely smaller and less coupled to uforth's suite layout.

Why it matters more than "one skipped workload"

The outlier is the one number that would move most if a Track O optimisation landed on the slow path, and the one most likely to regress unnoticed. A harness whose worst case is skipped reports only the cases that were already fine — the same shape as a green tier that skipped its corpus.

Note the harness is honest about it: a workload the base runtime cannot run is SKIPped with a reason, never emitted as a partial row. So this is a coverage gap, not a wrong number.

Gate

tools/uforth_bench.py --full emits ELF-HASH rows for cpython and pxx rather than a SKIP.

Deprioritised 2026-09-02 — the Track T tooling backlog was cut as a pile

This ticket is not being called wrong. It was moved as part of a pile, not judged individually, and nothing here disputes its finding.

Owner decision. 73 of the 74 open track: T tickets were filed between 2026-08-31 and 2026-09-02, 58 on one day. The pile was too large to work through and returned almost nothing, and a ticket nobody will fix does not sit neutrally — it stays in the ranker forever at zero value, which is the argument CLAUDE.md already makes for a terminal folder over a low prio.

Four were kept in the ranker on a purely structural test — an active umbrella or a hard blocked-by: edge from live work: umbrella-one-full-tier-run-with-no-red-tier, feature-t-freebsd-image-and-runner, and the two regression-test-core-* reds that block the umbrella.

Kept, not deleted, for two reasons: so the finding is not rediscovered and refiled from scratch by the next agent who trips over it, and so it can be pulled back if what it touches becomes load-bearing.

To revive it: move it to the owning lane's backlog, set status: backlog, and say in the ticket WHAT CHANGED to make it matter now. Restoring it because it reads well is how the pile comes back.