8000 rust: boot from rustc-1.98.1 as published in bootstrap gen-8 (mrustc ladder, both arches); the rungs leave pkgs by bryan-minimal · Pull Request #1210 · gominimal/pkgs · GitHub
[go: up one dir, main page]

Skip to content

rust: boot from rustc-1.98.1 as published in bootstrap gen-8 (mrustc ladder, both arches); the rungs leave pkgs - #1210

Closed
bryan-minimal wants to merge 2 commits into
mainfrom
bryan/rust-gen8
Closed

bryan-minimal wants to merge 2 commits into
mainfrom
bryan/rust-gen8

Conversation

@bryan-minimal
Copy link
Copy Markdown
Member

rust (1.99.1) now boots on both arches from rustc-1.98.1 as published in gen-8 of gominimal/bootstrap, and the nine lower rungs leave pkgs.

What gen-8 is

The Rust ladder, built in gominimal/bootstrap on the hex0-rooted toolchain roots, from source with no Rust binary as input: mrustc 0.12.0 (C++, built by the ladder's gcc) → mrustc-rustc-1.90.0 → rustc-1.91.1 → 1.92.0 → 1.93.1 → 1.94.1 → 1.95.0 → 1.96.0 → 1.97.1 → 1.98.1. These are pkgs' own rung recipes, ported unchanged but for their arch switch (pkgs collapses them to empty specs on arm64 and consumed sealed tarballs there; in bootstrap they build on both arches). Every rung was built on two independent machines per arch (amd64: an AMD c4d and an Intel c3; arm64: two Axions, one of which rebuilt the C roots from hex0 first) and admitted only when both produced identical trees: all twelve ladder packages on amd64, eleven of twelve on arm64, where mrustc's two binaries differ only in the CRC of a .gnu_debuglink to unshipped .debug files (recorded in the manifest; the 1.90.0 compiler they produced is identical). Objects live in gs://minimal-bootstrap/gen-8/sha256/<sha>/… (public read, create-only), listed in generations/gen-8/manifest.json and verified anonymously after upload.

Changed here

  • rustc-1.98.1: a prebuilt spec on both arches (layout usr/lib/rustc-1.98.1, same as the rung). Runtime deps are what the binaries link: the live llvm (libLLVM.so.21.1, link-shared as before, so an llvm soname bump still needs a new generation), openssl-3.5 (libssl.so.3, the ladder's openssl line), libssh2, zlib, sqlite, libffi and gcc's libgcc/libstdc++. The binaries run on the standard loader on both arches.
  • rust: only comments change; it still boots from /usr/lib/rustc-1.98.1.
  • Removed: mrustc, mrustc-rustc-1.90.0, rustc-1.91.1, rustc-1.92.0, rustc-1.93.1, rustc-1.94.1, rustc-1.95.0, rustc-1.96.0, rustc-1.97.1, and the 1.98.1 rung's build script, gates and answers. Only the next rung imported each.
  • hex0/amd64-ladder.ncl stays: the stage0-* C ladder and the bedrock roots still import it.

Cost

rust's spec hash moves on both arches (new stage0 Source), so everything Rust-built rebuilds once. The ladder itself no longer builds in any world.

🤖 Generated with Claude Code

…adder below it leaves pkgs

rustc-1.98.1 is now a prebuilt Source on both arches, the rustc-1.98.1
published in gen-8 (built there on the hex0-rooted toolchain from mrustc
and reproduced on two independent machines per arch). mrustc,
mrustc-rustc-1.90.0 and rustc-1.91.1 .. rustc-1.97.1 are removed; only
the next rung imported each. `rust` is unchanged apart from comments: it
still boots from /usr/lib/rustc-1.98.1.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@coderabbitai
coderabbitai Bot commented Oct 30, 2026
Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@bryan-minimal
Copy link
Copy Markdown
Member Author

Superseded by #1242, which merges this branch and repoints every bootstrap pin at gen-11 of gominimal/bootstrap. Closing to stop the duplicate world rebuilds; the branch stays.

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

0