Skip to content

docs: decisive test -- pipelining both cores does NOT fix the lottery; fault is outside the datapath (Refs #1764) - #1905

Merged
gHashTag merged 1 commit into
masterfrom
docs/pipeline-cores-does-not-fix-lottery
Aug 7, 2026
Merged

docs: decisive test -- pipelining both cores does NOT fix the lottery; fault is outside the datapath (Refs #1764)#1905
gHashTag merged 1 commit into
masterfrom
docs/pipeline-cores-does-not-fix-lottery

Conversation

@gHashTag

@gHashTag gHashTag commented Aug 7, 2026

Copy link
Copy Markdown
Owner

The decisive silicon experiment for the whole "pipeline the shared cores" branch (cycles 94-99).

Both shared cores were pipelined latency-1 with a register inside the combinational cloud (GftSmul_p2b cut mid-RNE, GftSadd_p2 cut mid-cascade), each verified bit-exact to its combinational core over 40-60k random operands (including zero and exact-cancellation corners). The integrated trainer is bit-exact in simulation and reaches fmax 32 MHz (vs 21 baseline).

On the AX7203, four seeds: 0/4 trained stably. Seeds 2 and 3 were near-model at ep0 (0/0.718/0.886/-0.011 and 0/0.551/1.021/0.506) then collapsed to all-zero by ep20 (the characteristic training-divergence glitch); seeds 1 and 4 glitched from ep0. This matches the baseline (~1/8 stable).

Conclusion: registering the core datapath — at the endpoints (cycle 97) or mid-cloud (now) — does not fix the fault. So the hazard is not in the GftSmul/GftSadd combinational datapath at all; it lives in the rf-write / control path (di decode, pc/settle/cen counters) or is a global placement effect. This closes the pipeline-the-cores branch and redirects the investigation. Added ruled-out item #10. (Sample is four seeds; base rate ~1/8, so 0/4 is indicative, not a proof of zero improvement.)

Board restored to the generated capstone (XOR 4/4). Docs-only. Refs #1764

… (Refs #1764)

Pipelined both shared cores latency-1 with a register INSIDE the combinational
cloud (GftSmul_p2b mid-RNE, GftSadd_p2 mid-cascade), each bit-exact to its
combinational core over 40-60k random operands; integrated trainer bit-exact
in sim, fmax 32 MHz. On the AX7203, 0/4 seeds trained stably (seeds 2,3
near-model at ep0 then collapsed by ep20; 1,4 glitched from ep0) -- same as
baseline. So registering the core datapath (endpoints in cycle 97, mid-cloud
now) does NOT fix the fault: the hazard is not in the GftSmul/GftSadd
datapath. Closes the pipeline-the-cores branch (cycles 94-99). Redirect to the
rf-write/control path (di decode, pc/settle/cen counters) and global placement
effects. Added ruled-out #10.

Refs #1764

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

📓 NotebookLM Notebook linked to this PR

This notebook contains session context, decisions, and artifacts for this work.

@github-actions

github-actions Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-08-07 20:29:36 UTC

Summary

Status Count
Total Open PRs 14
PRs with Failing Checks 1
PRs with All Checks Green 13
READY 5
FAILING 1
PENDING 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=2bd87d0d139e != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag
gHashTag merged commit 4010878 into master Aug 7, 2026
17 checks passed
@gHashTag
gHashTag deleted the docs/pipeline-cores-does-not-fix-lottery branch August 7, 2026 20:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant