Repository navigation
W974: the format's own operators on the real part — MHz/kLUT falls 32x, and the headline must name the operator and the clock - #681
Merged
Conversation
This was referenced Aug 21, 2026
Merged
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.
#680 gave the hardware axis its first number, for a classifier. This carries the format's own operators from spec to bitstream on
xc7a200tfbg676-1— Verilog generated throughout, no Docker involved.The measurements
mvp_ternary_classifiercfgmclkgft_saddslowclkgft_signed_macslowclkgft_signed_dot4slowclkAll timing PASS against their own constraints. Zero DSP48E1 in every design.
The clocks are not the same, and that matters for the headline
The classifier is constrained on
cfgmclk; thegft_*designs onslowclk. The 653 MHz/kLUT row is not comparable with the rest, and quoting all four as one ranking would repeat the unmatched-width error this project has already made four times.Within the comparable three, MHz/kLUT falls 13.9 → 1.41 → 0.43 — a factor of 32 across a 10× growth in area. And the shape is not linear in the operator:
sadd→mac: 4.9× the LUTs for half the frequencymac→dot4: 2.0× the LUTs for 0.6× the frequencySo a MHz/LUT figure quoted for one operator says almost nothing about another. A paper's single headline number must name which operator, on which clock.
The DUT-equivalent column is the honest denominator.
macreaches 3.10 DUT-equivalents of arithmetic on the die againstsadd's 1.06 — per unit of arithmetic actually delivered, the gap is far smaller than the raw LUT ratio suggests.Two unrelated failures on the fourth design
gft_signed_dot4finished synthesis (12 872 LUT, Fmax 5.50 MHz, PASS) and then went red twice, for different reasons:ABSENT, notFAIL. Nothing was proven unroutable; the run was stopped. Logged as a failure it would have entered the record as "does not route", which is a different and false claim.JTAG_CHAIN(3)enabled in the spec while the wrapper wiresBSCAN4. The service caught it; otherwise the bitstream would load and answer on the wrong chain.Two red stages, one evidence about the design and one about the time budget. Keeping
ABSENTandFAILin separate columns is what makes that distinction survivable.262 derived checks, all passing. Related: #680.
🤖 Generated with Claude Code