blog: 179 features that change no bits - #877
Open
gHashTag wants to merge 1 commit into
Open
Conversation
A parity report between the himbaechel xilinx port and nextpnr-xilinx 0.9.3 ranked its own work items backwards: the 179 missing BRAM features are zero-codepoints, and the blocker that kept a bitstream off a board produced no feature-count delta at all. Adds the post with receipts for #165, its two corrections, openXC7/nextpnr#1, prjxray-db#7, and the two open BUFIO items. Every measurement is attributed upstream; none was reproduced here, and that is stated in openQuestions. Co-Authored-By: Claude <noreply@anthropic.com>
Owner
Author
|
Status check, 2026-09-05. This PR has been open since 2026-08-31 with no activity — flagging it rather than letting it go quiet indefinitely. Both CI failures look like repo-wide gates, not content issues:
The PR body already defers the merge decision to the operator ("Not merging — publication is the operator's decision"). Restating that here so it's visible without needing to open the diff: this is ready for a merge/hold/close call whenever convenient, not something blocking on more work. |
gHashTag
added a commit
to gHashTag/trinity-fpga
that referenced
this pull request
Sep 5, 2026
…n a real disk crisis
Posted the PR #877 status-check comment per explicit operator go-ahead
("post it as-is") after drafting it on request:
gHashTag/trinity#877 (comment).
Investigating before drafting corrected a standing mischaracterization from
OD3/OD9: #877 is the operator's own PR (authored via an earlier Claude Code
session, in their own repo), not a third-party-adjacent one needing extra
publish caution. Also found why it looked stuck: "Brain Health Check" is a
repo-wide CI gate that ran full brain-region tests against a blog-post-only
diff touching no brain code, and its own failure-comment bot hit an
unrelated 403 permissions bug. The PR body had already deferred the merge
call to the operator from the start -- not neglect, a parked proposal.
Separately: this cycle opened with a real disk crisis (0.18 GiB, then 127
MiB free) -- the third this session. It resolved on its own (disk recovered
to ~20 GiB, /tmp state including the compiled binary was gone, consistent
with a reboot or cache-clear outside this loop's control) before any
action was needed. This gave B21's hysteresis its first real-world test:
the first post-crisis reading correctly held the verdict at HALT for one
more confirmation despite the raw reading already showing recovery, then
cleared on the second confirming reading -- exactly the designed behavior,
now proven against production data instead of only a scratch copy.
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
1 participant
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.
Adds one blog post:
features-that-change-no-bits, dated 2026-08-31.What it reports
Material from the last 24 hours in
openXC7/nextpnr-xilinx#165, plus the mergedchanges it depends on:
as "the most concrete bitstream-parity item and the one I would fix first".
proven three independent ways (segbits, a
bit2fasmround trip givingbyte-identical 5 576 340 B frames in both arms, and a Vivado ML 2026.1 golden).
produced no feature-count delta and failed in two different-looking ways
depending on the prjxray-db revision.
being the one carrying
openXC7/nextpnr#1.Honesty notes
cavearr's in fix(state): add missing child.deinit() in tri_state.zig runProcessInherit #165; the board run is jrrk2's on his own Sonata. This is stated
in the body and again as the first
openQuestionsentry.fix(state): add missing child.deinit() in tri_state.zig runProcessInherit #165 OPEN, refactor(faculty): extract hardcoded paths to constants in faculty_board.zig #168 OPEN, feat(cloud): add API key validation before spawning agent container #149 OPEN,
openXC7/nextpnr#1MERGED 2026-08-29,openXC7/prjxray-db#7MERGED 2026-08-26.quoteblocks rather thanparaphrased into something stronger — including "to our knowledge" on the
first-board-verified claim.
comparable between trees, the BRAM address cascade unverified on silicon, and
the regional clock path routed around rather than fixed.
ruis complete: title, summary, openQuestions and body.Build
npm run build:ciexits 0; the slug appears indist/assets/Blog-D9NOt413.jsand gets its own chunk
features-that-change-no-bits-DCKQ1Tl1.js.Not merging — publication is the operator's decision.
🤖 Generated with Claude Code