Change: GNU Toolchain Update #3641

Closed
opened 2026-07-14 11:23:41 +00:00 by amoloney · 4 comments
Owner

Update the Fedora 45 GNU Toolchain to gcc 16.2, binutils 2.47, glibc 2.44 and gdb 17.2.

Please note the related change request that includes enabling Shadow Stack support by default in glibc, which is described as a separate "Shadow Stack" system-wide change request for Fedora 45.

The set of core GNU Toolchain packages for Fedora 45 are as follows:

GNU C Compiler 16.2
    Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), Fortran (gfortran), D (phobos), Objective C/C++.
GNU Binary Utilities 2.47
GNU C Library 2.44
GNU Debugger 17.2 (immediately available in all Fedora releases)

The gcc 16.2 change will be tracked in this top-level GNU Toolchain system-wide change request.

The binutils 2.47 change will be tracked in this top-level GNU Toolchain system-wide change request.

The glibc 2.44 change will be tracked in this top-level GNU Toolchain system-wide change request.

The gdb 17.2 update will be rolled out across all Fedora releases and the move to newer versions will be handled in the same fashion. The debugger is capable of debugging the binary artifacts produced by the rest of the system toolchain.

Owners, do not implement this work until the FESCo vote has explicitly ended.
When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the FESCo ticket policy and the Changes policy for more information.
If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update.

REMINDER: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the Fedora Devel mailing list.

Update the Fedora 45 GNU Toolchain to gcc 16.2, binutils 2.47, glibc 2.44 and gdb 17.2. Please note the related change request that includes enabling Shadow Stack support by default in glibc, which is described as a separate "Shadow Stack" system-wide change request for Fedora 45. The set of core GNU Toolchain packages for Fedora 45 are as follows: GNU C Compiler 16.2 Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), Fortran (gfortran), D (phobos), Objective C/C++. GNU Binary Utilities 2.47 GNU C Library 2.44 GNU Debugger 17.2 (immediately available in all Fedora releases) The gcc 16.2 change will be tracked in this top-level GNU Toolchain system-wide change request. The binutils 2.47 change will be tracked in this top-level GNU Toolchain system-wide change request. The glibc 2.44 change will be tracked in this top-level GNU Toolchain system-wide change request. The gdb 17.2 update will be rolled out across all Fedora releases and the move to newer versions will be handled in the same fashion. The debugger is capable of debugging the binary artifacts produced by the rest of the system toolchain. * [Change proposal](https://fedoraproject.org/wiki/Changes/GNUToolchainF45) * [devel post](https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/JVBSI5YKY2XRPG2NWKOORPQY433ZLX5P/) * [Discourse discussion](https://discussion.fedoraproject.org/t/f45-change-proposal-gnu-toolchain-update-system-wide/195273) * Owners: @codonell **Owners, do not implement this work until the FESCo vote has explicitly ended.** When a FESCo member has marked this ticket as APPROVED, you may proceed with the implementation. See the [FESCo ticket policy](https://docs.fedoraproject.org/en-US/fesco/#_ticket_policy) and the [Changes policy](https://docs.fedoraproject.org/en-US/program_management/changes_policy/) for more information. If no decision has been rendered after 7 days from the filing of this ticket and no indication (such as a -1 vote) that this will be taken up at a FESCo meeting, please feel free to ping for a status update. **REMINDER**: This ticket is for FESCo members to vote on the proposal. Further discussion should happen in the Discourse discussion linked above. Additional discussion may happen on the [Fedora Devel](https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/) mailing list.
Owner

+1

+1
Owner

+1

+1

The glibc update in https://bodhi.fedoraproject.org/updates/FEDORA-2026-54318fdaca is good enough for a mass rebuild, it was updated from the upstream development branch by Frederic on the 7th.

The gcc update in https://bodhi.fedoraproject.org/updates/FEDORA-2026-9a7eae5a85 is good enough for a mass rebuild, it was updated from the upstream release branch by Jakub on the 3rd.

The binutils update in https://bodhi.fedoraproject.org/updates/FEDORA-2026-aa53457f70 is undergoing final review by Siddhesh and Nick. The previous build https://bodhi.fedoraproject.org/updates/FEDORA-2026-547ddbb113 is in theory good enough for a mass rebuild.

The gdb update in https://bodhi.fedoraproject.org/updates/FEDORA-2026-4a670576d0 is good enough for a mass rebuild, it was updated by Kevin on the 13th.

I think we are green from the system toolchain perspective except the binutils update is stuck under review, but we're working on that.

The glibc update in https://bodhi.fedoraproject.org/updates/FEDORA-2026-54318fdaca is good enough for a mass rebuild, it was updated from the upstream development branch by Frederic on the 7th. The gcc update in https://bodhi.fedoraproject.org/updates/FEDORA-2026-9a7eae5a85 is good enough for a mass rebuild, it was updated from the upstream release branch by Jakub on the 3rd. The binutils update in https://bodhi.fedoraproject.org/updates/FEDORA-2026-aa53457f70 is undergoing final review by Siddhesh and Nick. The previous build https://bodhi.fedoraproject.org/updates/FEDORA-2026-547ddbb113 is in theory good enough for a mass rebuild. The gdb update in https://bodhi.fedoraproject.org/updates/FEDORA-2026-4a670576d0 is good enough for a mass rebuild, it was updated by Kevin on the 13th. I think we are green from the system toolchain perspective except the binutils update is stuck under review, but we're working on that.
Owner

We discussed this during the meeting yesterday:
AGREED: Approve GNU Toolchain Change for F44 (+6, 1, 0)
ACTION: gotmax to create ticket to make Major Toolchain Updates/Changes schedule item a week before the mass
rebuild

Please coordinate with releng how to push the updates before the mass rebuild.

We discussed this during the meeting yesterday: AGREED: Approve GNU Toolchain Change for F44 (+6, 1, 0) ACTION: gotmax to create ticket to make Major Toolchain Updates/Changes schedule item a week before the mass rebuild Please coordinate with releng how to push the updates before the mass rebuild.
Sign in to join this conversation.
No milestone
No project
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
fesco/tickets#3641
No description provided.