riscv64: pin tcc 0.9.26-1157-gdd46e018 (1147's tcc-mes cannot build through) - #583
Open
JasonGross wants to merge 1 commit into
Open
riscv64: pin tcc 0.9.26-1157-gdd46e018 (1147's tcc-mes cannot build through)#583JasonGross wants to merge 1 commit into
JasonGross wants to merge 1 commit into
Conversation
fosslinux
requested changes
Jul 27, 2026
fosslinux
left a comment
fosslinux
left a comment
Owner
There was a problem hiding this comment.
this doesn't make sense to me, why have different versions for riscv64 and everything else?
Author
|
Yeah, that's a good point, I guess the LLM was trying to code "defensively" by only changing things it tested. I will fix. |
The 1147 tcc-mes cannot build through on riscv64. Advance the single pin for all architectures rather than diverging the pin per-architecture. 1157 also changes i386 code generation (it adds gen_cvt_csti), so the x86 tcc binaries change. Checksums were regenerated with a full x86 chroot run (./rootfs.py --chroot --update-checksums) that ran to the end of the manifest.
JasonGross
force-pushed
the
riscv64-tcc-1157-pin
branch
from
July 27, 2026 18:14
4dab780 to
d29c28f
Compare
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
2 participants
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.
Fixes #582.
riscv64-only bump of the tcc-0.9.26 step to tcc-0.9.26-1157-gdd46e018.
x86 keeps 1147 and its checksums; the step's fileopen simple-patches
apply unchanged to 1157's tcctools.c. Why 1147 cannot build through on
riscv64 -- a MesCC-tripped range assert that 1157 casts to (uint32_t),
and a missing .option directive that mes-0.27.1's crt1.c needs -- is
in the issue.
Contents:
lilypond.org directory (sha256 3748c0aa...).
riscv64, in the file's existing arch-conditional style.
(1020608 bytes), the MesCC-built 1157 binary. Measured by a replay
of this step's recipe; the same replay reproduces the current pin
3e2d226b... byte-exactly when pointed at 1147, which is our evidence
the recipe is faithful. We could not run the full in-tree bootstrap
here.
The downstream entries are left as recorded: they are already the 1157
lineage's outputs. The one we verified byte-exactly is crt1.o
cc417e9d... -- our replay's self-rebuilt 1157, the recorded pin, and
the tcc that Guix's riscv64 bootstrap builds all agree on it. A run
with UPDATE_CHECKSUMS=True would confirm the whole file from one
lineage; we changed only what we measured rather than guess the rest.
Authorship note: this pull request was researched, written, and posted
by Claude (Anthropic's Fable 5 model), working on Jason Gross's behalf.