Skip to content

fix(build): all musl paths on gcc 16.1.0 — delete the GCC-15 instantiation anchor (A2 complete)#204

Merged
Sunrisepeak merged 2 commits into
mainfrom
feat/musl-gcc16-drop-anchor
Jul 9, 2026
Merged

fix(build): all musl paths on gcc 16.1.0 — delete the GCC-15 instantiation anchor (A2 complete)#204
Sunrisepeak merged 2 commits into
mainfrom
feat/musl-gcc16-drop-anchor

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

musl-gcc 16.1.0 shipped (stripped dual-arch, GitHub+GitCode, xim #345 gated by the consumer smoke). Native x86_64 static release build, native aarch64 and cross all move to GCC 16; the force_template_instantiations() anchor loses its last consumer and is deleted — this PR's musl/cross links ARE the regression test. Local verification: anchor-free static builds green on both targets with GCC: (GNU) 16.1.0 ELF notes. Design: .agents/docs/2026-07-08-root-cause-remediation-design.md A2.

…ation anchor (A2 complete)

musl-gcc 16.1.0 shipped (stripped, dual-arch, GitHub+GitCode; xim entry
openxlings/xim-pkgindex#345, gated by the consumer smoke). With every
musl path on GCC 16 — native x86_64 (release static build), native
aarch64, and cross — the force_template_instantiations() anchor loses
its last consumer and is deleted. This commit is the regression test:
if any floor didn't take, the musl/cross links go red.
The anchor-removal build actually succeeded (Resolved gcc@16.1.0-musl);
the red came from ci-linux's hardcoded 'Resolved gcc@15.1.0-musl'
assertion. Update every musl 15.1.0 reference across workflows.
@Sunrisepeak Sunrisepeak merged commit a4cdae0 into main Jul 9, 2026
6 of 7 checks passed
@Sunrisepeak Sunrisepeak deleted the feat/musl-gcc16-drop-anchor branch July 9, 2026 05:12
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