Repository navigation
Conversation
…untimes Co-authored-by: phlax <454682+phlax@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update GCC toolchain for backward compatibility with libstdc++
Follow-up to #5490: preserve sysroot compatibility and validate GCC runtimes
Oct 25, 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.
Layers review follow-ups onto
copilot/gcc-toolchain-hermetic-fix, retaining hermetic GCC 13.4.0, a shared base sysroot, and static C++ runtimes. Preserves downstream compatibility while providing a migration path away from libstdc++ sysroot variants.stdcc_version, published hashes, and download URLs. Pin deprecated variants to their existing release; preserve release metadata without rebuilding them.:libstdcxxand:libgcctargets, CcInfo analysis coverage, and prefixer migration guidance:Release dependency: Rebuild both wee8 libstdc++ archives and publish their hashes in the next
bins-v*release. The linked probe remains hash-gated until the incompatible x86_64 prebuilt is replaced; aarch64 awaits its first archive.