Repository navigation
W976: zero is not an annihilator in the generated MAC — reproduced off the die in 25 microseconds - #685
Merged
Conversation
This was referenced Aug 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Zero is not an annihilator in the generated signed MAC — and the die only had to ask
#684 reported
gft_signed_macansweringclauses=0011, ok=0on silicon. That word decodes exactly against the layout the wrapper documents:mac(0, live, 0, live2) == 0mac(live,TWO,live2,ONE) == mac(TWO,live,ONE,live2)mac(ONE, live, NEG, live) == 0test cancelmac(live, ONE, live2, ONE) != 0test ppZERO is a logic defect, and a board is not needed to see it
Driving the same generated Verilog in icarus with the wrapper's own operands:
The result is
512 + 4·live, independent oflive2over the range probed. Multiplying by zero does not produce zero, and the residue grows linearly with one operand. Reproduced in 25 µs of simulated time; the testbench is committed astb_zero_comm_w976.v.The die's entire contribution was to ask a question nobody had asked.
COMM is confirmed on silicon and unexplained off it
live,live2 = 7·live0x7FFFFFFF,0x80000000,0xFFFFFFFFThe third attempt tested a specific mechanism: the clause registers are sticky (
if (!comm_ok) c_comm <= 1'b0) and the comparison is not gated on the tworeadysignals, so a single disagreeing cycle would latch the clause false forever. No such cycle occurs, andreadynever diverges between the two instances.Stated as unexplained on purpose. This project has mis-attributed hardware three times in three waves — "Docker is the blocker", "the cable is missing", "the bitstream has no BSCANE2" — and each was a plausible guess. Remaining candidates: a physical effect (against a 4.1× timing margin), or an operand sequence the die reaches over hours that a bounded sweep does not.
The suite covered exactly the clauses that pass
ZERO and COMM: untested. CANCEL and IND: tested, and green on the die. The correspondence is exact in both directions.
And the spec's two tests are weak in a second, independent way — they assert on fixed constants:
while every die clause drives live operands that change each beat. A test that supplies one operand value cannot see a residue that grows with the operand — which is exactly what the ZERO defect is.
293 derived checks, all passing. Related: #683, #684.
🤖 Generated with Claude Code