Skip to content

[WIP] gcc: update to 16.1.1+20260502.#60505

Draft
oreo639 wants to merge 42 commits into
void-linux:masterfrom
oreo639:gcc16
Draft

[WIP] gcc: update to 16.1.1+20260502.#60505
oreo639 wants to merge 42 commits into
void-linux:masterfrom
oreo639:gcc16

Conversation

@oreo639
Copy link
Copy Markdown
Member

@oreo639 oreo639 commented May 11, 2026

Testing the changes

  • I tested the changes in this PR: briefly

[ci skip]

This restricts musl1.1 to specifically armv* architectures rather than all 32-bit architectures since armv* are the only ones officially supported.

I have removed the patches for --enable-autolink-libatomic as support for that was merged into gcc upstream.

I have also enabled libsanitizer for musl architectures.

TODO: libphobos currently fails to build on armv7l-musl and armv6l-musl, I did try reworking the time_t patch for the changes to libphobos but I haven't gotten it working atm. I have removed the patch for now. I can confirm the same issue happens on the latest release of ldc (2.42.x) as well. I have disabled gdc on those architectures temporarily until I have the time to fully debug it.

I also have yet to update the cross compilers (which I will do soon) or run a full test of the core packages as well as anything pulled in by the ISOs, which I will do when I have the time.

Note for merging: glibc and musl must be merged and built before everything else.

@oreo639 oreo639 force-pushed the gcc16 branch 2 times, most recently from 85cb438 to e7cc8a6 Compare May 11, 2026 20:28
@oreo639 oreo639 force-pushed the gcc16 branch 6 times, most recently from 47803cb to 97e0eed Compare May 12, 2026 08:24
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