summaryrefslogtreecommitdiff
path: root/src/data.c
diff options
context:
space:
mode:
authorScott Gasch <[email protected]>2026-09-04 09:50:57 -0700
committerScott Gasch <[email protected]>2026-09-04 09:50:57 -0700
commit5c3e541b3bf62704eb8950441646deacaea6f887 (patch)
tree46f41902be36c27075bbb66008810cdfad1aa14a /src/data.c
parent1f638f87d8afb0334bf05dda10dc13b4c7a60b62 (diff)
Record whole-engine sd10 results: zero solve regression, +8.38% NPS
Board-representation migration section 4 item 5 / section 5 item 2 / section 7: ran all three curated suites (ecm_ringers, ecm_confident_quick, ecm_hard_quick) at sd10, same commit built twice (default asm GetAttacks vs. GETATTACKS_BITBOARD=1), rather than against the checked-in head_reference/ binary -- that binary predates this branch's sections 1-6 by a dozen-plus unrelated commits, so diffing against it would have conflated this change with everything else on the branch. Isolating the single variable (same commit, one flag flipped) is the correct comparison here. Results: solve counts bit-identical on all three suites (10/11, 83/90, 25/90) -- zero regression. Node counts up slightly (+0.36% to +1.24%), the expected "same attacker set, not necessarily same order" effect on move-ordering tie-breaking already flagged in this document; didn't cost a single solve. Aggregate (total nodes / total script time across all three suites): +8.38% wall-clock NPS (1,164,842 -> 1,262,490), comfortably absorbing the extra nodes -- confirms section 3's isolated cycles/call benchmark reflects a real end-to-end win, not an artifact of the isolated harness. match_play.py (the remaining section 7 criterion) deliberately deferred, not run this pass. Co-Authored-By: Claude Sonnet 5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Jntky4yGUTyQVaGCXms4F2
Diffstat (limited to 'src/data.c')
0 files changed, 0 insertions, 0 deletions