Latest revision as of 16:54, 2 October 2024

GNU Toolchain Update (gcc 14+, binutils 2.42+, glibc 2.40, gdb 14+)

Summary

Update the Fedora 41 GNU Toolchain to gcc 14.1+, binutils 2.42+, glibc 2.40 and gdb 14+.

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

GNU C Compiler 14.1+
- Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), Fortran (gfortran), D (phobos), Objective C/C++.
GNU Binary Utilities 2.42+
GNU C Library 2.40
GNU Debugger 14+ (immediately available in Fedora 40)

The gcc 14.1+ change will be tracked in this top-level GNU Toolchain system-wide update.

The binutils 2.42+ change will be tracked in this top-level GNU Toolchain system-wide update.

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

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

Owner

Name: Carlos O'Donell
Email: carlos@redhat.com

Current status

Targeted release: Fedora Linux 41
Last updated: 2024-10-02
Announced
Discussion Thread
FESCo Ticket: #3181
Updated redhat-rpm-config: [] (TODO: Check if redhat-rpm-config needs updating for the new toolchain)
- Are config.guess and config.sub up to date from upstream?
GCC Ada SONAME bump: [x] No. Fedora 41 has no Ada SONAME change. The SONAME bump happened in Fedora 40.
Tracker bug: #2274811
Release notes tracker: #109

Detailed Description

The GNU Compiler Collection, GNU Binary Utilities, GNU C Library, and the GNU Debugger make up the core part of the GNU Toolchain and it is useful for our users to transition these components as a complete implementation when making a new release of Fedora.

The GNU Compiler Collection is expected to release version 14.1+ (point release), before the Fedora 41 release. It will contain many new features, documented here: https://gcc.gnu.org/gcc-14/changes.html. The latest point release for gcc 14.1+ will be included in Fedora 41, this will most probably be 14.2 or later.

The GNU Binutils version 2.42 was released before Fedora 41; and we have already been using this version of binutils in Fedora Rawhide successfully to build the distribution. Given the present schedule for Fedora 41 we will continue to use Binutils 2.42 or 2.43 if deemed stable enough. As an experiment we will be trying out more frequent updates to the rawhide binutils, so that it remains closer to the upstream master sources. Currently rawhide binutils is synced twice a year, bu the plan is to try syncing monthly or maybe every fortnight.

The GNU C Library version 2.40 is expected to be release before Fedora 41; we have started closely tracking the glibc 2.40 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 41 will branch after the release of glibc 2.40. However, the mass rebuild schedule means Fedora 41 will mass rebuild (if required) before the final release of glibc 2.40, but after the ABI is frozen.

The GNU Debugger version 14+ has already been rolled out across all Fedora releases at the same time.

Benefit to Fedora

Stays up to date with latest features, improvements, security and bug fixes from gcc, glibc, binutils, and gdb upstream.

The goal is to track and transition to the latest components of the GNU Toolchain.

Scope

Proposal owners: Fedora Toolchain Team (gcc, glibc, binutils, gdb, ...) developers need to ensure that gcc, glibc, binutils, and gdb in rawhide are stable and ready for the Fedora 41 branch.

Other developers: Given that glibc is backwards compatible and we have been testing the new glibc in rawhide it should make very little impact when updated, except for the occasional deprecation warnings and removal of legacy interfaces from public header files.

Release engineering: A mass rebuild is strongly encouraged; #11898

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with Objectives: N/A

Upgrade/compatibility impact

The compiler, the static linker and the the library are backwards compatible with the previous version of Fedora.

Any source level changes required for glibc 2.40 will be noted here: https://sourceware.org/glibc/wiki/Release/2.40#Packaging_Changes

How To Test

The GNU Compiler Collection has its own test suite which is run during the package build and examined by the gcc developers before being uploaded.

The GNU C Library has its own test suite which is run during the package build and examined by the glibc developers before being uploaded. This test suite has over 6200 tests that run to verify the correct operation of the library. In the future we may also run the microbenchmark to look for performance regressions.

The GNU Binutils has its own test suite which is run during the package build and examined by binutils developers before being uploaded. The regression test suite is run to verify the correct operation of the static linker and attendant utilities.

The GNU Debugger has its own test suite which is run during the package build and examined by gdb developers before being uploaded. The regression test suite is run to verify the correct operation of the debugger.

User Experience

Upgrading the 4 main GNU Toolchain components (gcc, binutils, glibc, and gdb) ensures that users have an up to date working system compiler, assembler, static linker, core language runtimes (C, C++, etc), dyanmic linker, and debugger. All of these components are being updated to provide support for newer language features, and hardware features; enabling users to make use of these features for their applications. In some cases the components are updated in a synchronized fashion if a feature requires support across the components that constitute the implementation e.g. compiler feature that requires language library support.

Dependencies

All packages do not need to be rebuilt due to backwards compatibility. However, it is advantageous if a mass rebuild is performed during the Fedora 41 cycle. The mass rebuild would ensure all packages can be built with the newer compiler and core runtime.

Contingency Plan

Contingency mechanism glibc: If glibc 2.40 proves too disruptive to compiling the distribution we could revert to 2.39, but given that Rawhide has started tracking glibc 2.40, no show-stopper problems are expected. At this point we can still revert to upstream version 2.39 if insurmountable problems appear, but to do so may require a mass rebuild to remove new symbols from the ABI/API.

Contingency mechanism binutils: If binutils 2.42 proves too distruptive to assembling and linking the distribution we could revert to 2.41, but given that Rawhide is using 2.42, no show-stopper problems are expected. At this point we can still revert if insurmountable problems appear, but to do so may require a mass rebuild if the defects involve generated binaries.

Contingency mechanism for gcc: If gcc 14.1+ proves too disruptive to compiling the distribution we could revert to gcc 14.0.

Contingency deadline: Fedora mass rebuild on 2024-07-17.
Blocks release?
- No, upgrading to gcc 14+ does block the release.
- Yes, upgrading to binutils 2.42 does block the release.
- Yes, upgrading to glibc 2.40 does block the release.
- No, upgrading to gdb 14+ does not block the release.

Documentation

The gcc manual contains the documentation for the release and doesn't need any more additional work.

The binutils manual contains the documentation for the release and doesn't need any more additional work.

The glibc manual contains the documentation for the release and doesn't need any more additional work.

The gdb manual contains the documentation for the release and doesn't need any more additional work.

Release Notes

See https://gcc.gnu.org/gcc-14/changes.html for the GNU Compiler Collection version 14 release notes.

The GNU C Library version 2.40 will be released at the beginning of August 2024. The current NEWS notes can be seen here as they are added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD

The GNU Binary Utilities version 2.42 was released February 2024. The current release notes will be sent to the developer mailing list.

@@ Line 1: / Line 1: @@
 <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name.  This keeps all change proposals in the same namespace -->
-{{admon/important|This page is an incomplete template|The Fedora Platform Tools team uses this page as the template for the GNU Toolchain updates for each Fedora release. The page should be kept in sync with the generic template: https://fedoraproject.org/wiki/Changes/EmptyTemplate}}
+= GNU Toolchain Update (gcc 14+, binutils 2.42+, glibc 2.40, gdb 14+) <!-- The name of your change proposal --> =
-= GNU Toolchain Update (gcc X.Y, binutils X.Y, glibc X.Y, gdb X.Y) <!-- The name of your change proposal --> =
 == Summary ==
 <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. Note that motivation for the change should be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->
-Update the Fedora XX GNU Toolchain to gcc X.Y, binutils X.Y, glibc X.Y and gdb X.Y.
+Update the Fedora 41 GNU Toolchain to gcc 14.1+, binutils 2.42+, glibc 2.40 and gdb 14+.
-The set of core GNU Toolchain packages for Fedora 3XX are as follows:
+The set of core GNU Toolchain packages for Fedora 41 are as follows:
-* GNU C Compiler X.Y
+* GNU C Compiler 14.1+
 ** Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), Fortran (gfortran), D (phobos), Objective C/C++.
-* GNU Binary Utilities X.Y
+* GNU Binary Utilities 2.42+
-* GNU C Library X.Y
+* GNU C Library 2.40
-* GNU Debugger X.Y (immediately available in Fedora XX)
+* GNU Debugger 14+ (immediately available in Fedora 40)
-The gcc X.Y change will be tracked in this top-level GNU Toolchain system-wide update.
+The gcc 14.1+ change will be tracked in this top-level GNU Toolchain system-wide update.
-The binutils X.Y change will be tracked in this top-level GNU Toolchain system-wide update.
+The binutils 2.42+ change will be tracked in this top-level GNU Toolchain system-wide update.
-The glibc X.Y change will be tracked in this top-level GNU Toolchain system-wide update.
+The glibc 2.40 change will be tracked in this top-level GNU Toolchain system-wide update.
-The gdb X.Y update was rolled out across all Fedora releases and the move to X+ will be handled in the same fashion. The debugger is capable of debugging the binary artifacts produced by the rest of the system toolchain.
+The gdb 14+ update was rolled out across all Fedora releases and the move to 14+ will be handled in the same fashion. The debugger is capable of debugging the binary artifacts produced by the rest of the system toolchain.
 == Owner ==
@@ Line 39: / Line 40: @@
 == Current status ==
-[[Category:ChangePageIncomplete]]
+[[Category:ChangeAcceptedF41]]
 <!-- When your change proposal page is completed and ready for review and announcement -->
 <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->
@@ Line 49: / Line 50: @@
 [[Category:SystemWideChange]]
-* Targeted release: [[Releases/XX | Fedora Linux XX ]]
+* Targeted release: [[Releases/41 | Fedora Linux 41 ]]
 * Last updated: <!-- this is an automatic macro — you don't need to change this line -->  {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
 <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page
@@ Line 57: / Line 58: @@
 ON_QA -> change is fully code complete
 -->
-* [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/72MYJW4PQENMESOXB5QIIBSJU3GUVEDX/ devel thread]
+* [https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org/thread/IZLWTFBWT52JMPLDBAHUYZ7LJ3FVPRQE/ Announced]
+* [https://discussion.fedoraproject.org/t/f41-change-proposal-gnutoolchain-system-wide/107509 Discussion Thread]
+* FESCo Ticket: [https://pagure.io/fesco/issue/3181 #3181]
 * Updated redhat-rpm-config: [] (TODO: Check if redhat-rpm-config needs updating for the new toolchain)
 ** Are config.guess and config.sub up to date from upstream?
-* GCC Ada SONAME bump: [] (TODO: Check if Ada bumped the SONAME)
+* GCC Ada SONAME bump: [x] No. Fedora 41 has no Ada SONAME change. The SONAME bump happened in Fedora 40.
-** Did we rebuild the packages in the side-tag before merging?
+* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2274811 #2274811]
-* FESCo issue: [https://pagure.io/fesco/issue/XX #XX]
+* Release notes tracker: [https://gitlab.com/fedora/docs/fedora-linux-documentation/release-notes/-/issues/109 #109]
-* Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=XX #XX]
-* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/XX #XX]
 == Detailed Description ==
@@ Line 72: / Line 73: @@
 <!-- Use this text for a GCC update: -->
-The GNU Compiler Collection is expected to release version X.Y, before the Fedora XX release. It will contain many new features, documented here: https://gcc.gnu.org/gcc-X/changes.html. The latest point release for gcc X will be included in Fedora XX, this will most probably be X.Y.
+The GNU Compiler Collection is expected to release version 14.1+ (point release), before the Fedora 41 release. It will contain many new features, documented here: https://gcc.gnu.org/gcc-14/changes.html. The latest point release for gcc 14.1+ will be included in Fedora 41, this will most probably be 14.2 or later.
 <!-- Use this text for a BINUTILS update: -->
-The GNU Binutils version X.Y was released before Fedora XX; and we have already been using this version of binutils in Fedora Rawhide successfully to build the distribution. Given the present schedule for Fedora XX we will continue to use Binutils X.Y.
+The GNU Binutils version 2.42 was released before Fedora 41; and we have already been using this version of binutils in Fedora Rawhide successfully to build the distribution. Given the present schedule for Fedora 41 we will continue to use Binutils 2.42 or 2.43 if deemed stable enough.  As an experiment we will be trying out more frequent updates to the rawhide binutils, so that it remains closer to the upstream master sources.  Currently rawhide binutils is synced twice a year, bu the plan is to try syncing monthly or maybe every fortnight.
 <!-- Use this text for a GLIBC update: -->
-The GNU C Library version X.Y is expected to be release before Fedora XX; we have started closely tracking the glibc X.y development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora XX will branch after the release of glibc X.Y. However, the mass rebuild schedule means Fedora XX will mass rebuild (if required) before the final release of glibc X.Y, but after the ABI is frozen.
+The GNU C Library version 2.40 is expected to be release before Fedora 41; we have started closely tracking the glibc 2.40 development code in Fedora Rawhide and are addressing any issues as they arise. Given the present schedule Fedora 41 will branch after the release of glibc 2.40. However, the mass rebuild schedule means Fedora 41 will mass rebuild (if required) before the final release of glibc 2.40, but after the ABI is frozen.
 <!-- Use this text for a GDB update: -->
-The GNU Debugger version X.Y has already been rolled out across all Fedora releases at the same time.
+The GNU Debugger version 14+ has already been rolled out across all Fedora releases at the same time.
 == Benefit to Fedora ==
@@ Line 117: / Line 118: @@
 == Scope ==
-* Proposal owners: Fedora Toolchain Team (gcc, glibc, binutils, gdb, ...) developers need to ensure that gcc, glibc, binutils, and gdb in rawhide are stable and ready for the Fedora XX branch. <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
+* Proposal owners: Fedora Toolchain Team (gcc, glibc, binutils, gdb, ...) developers need to ensure that gcc, glibc, binutils, and gdb in rawhide are stable and ready for the Fedora 41 branch. <!-- What work do the feature owners have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
 * Other developers: Given that glibc is backwards compatible and we have been testing the new glibc in rawhide it should make very little impact when updated, except for the occasional deprecation warnings and removal of legacy interfaces from public header files. <!-- What work do other developers have to accomplish to complete the feature in time for release?  Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?-->
-* Release engineering: A mass rebuild is strongly encouraged; [https://pagure.io/releng/issue/XX #XX]
+* Release engineering: A mass rebuild is strongly encouraged; [https://pagure.io/releng/issue/11898 #11898]
 <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)?  Is a mass rebuild required?  include a link to the releng issue.
 The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication -->
@@ Line 143: / Line 144: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-Any source level changes required for glibc X.Y will be noted here: https://sourceware.org/glibc/wiki/Release/X.Y#Packaging_Changes
+Any source level changes required for glibc 2.40 will be noted here: https://sourceware.org/glibc/wiki/Release/2.40#Packaging_Changes
 == How To Test ==
@@ Line 189: / Line 190: @@
 == Dependencies ==
 <!-- What other packages (RPMs) depend on this package?  Are there changes outside the developers' control on which completion of this change depends?  In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate?  Other upstream projects like the kernel (if this is not a kernel change)? -->
-All packages do not need to be rebuilt due to backwards compatibility. However, it is advantageous if a mass rebuild is performed during the Fedora XX cycle. The mass rebuild would ensure all packages can be built with the newer compiler and core runtime.
+All packages do not need to be rebuilt due to backwards compatibility. However, it is advantageous if a mass rebuild is performed during the Fedora 41 cycle. The mass rebuild would ensure all packages can be built with the newer compiler and core runtime.
 == Contingency Plan ==
 <!-- If you cannot complete your feature by the final development freeze, what is the backup plan?  This might be as simple as "Revert the shipped configuration".  Or it might not (e.g. rebuilding a number of dependent packages).  If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy.  -->
-* Contingency mechanism glibc: If glibc X.Y proves too disruptive to compiling the distribution we could revert to X.Y-1, but given that Rawhide has started tracking glibc X.Y, no show-stopper problems are expected.  At this point we can still revert to upstream version X.Y-1 if insurmountable problems appear, but to do so may require a mass rebuild to remove new symbols from the ABI/API.
+* Contingency mechanism glibc: If glibc 2.40 proves too disruptive to compiling the distribution we could revert to 2.39, but given that Rawhide has started tracking glibc 2.40, no show-stopper problems are expected.  At this point we can still revert to upstream version 2.39 if insurmountable problems appear, but to do so may require a mass rebuild to remove new symbols from the ABI/API.
-* Contingency mechanism binutils: If binutils X.Y proves too distruptive to assembling and linking the distribution we could revert to X.Y-1, but given that Rawhide is using X.Y, no show-stopper problems are expected. At this point we can still revert if insurmountable problems appear, but to do so may require a mass rebuild if the defects involve generated binaries.
+* Contingency mechanism binutils: If binutils 2.42 proves too distruptive to assembling and linking the distribution we could revert to 2.41, but given that Rawhide is using 2.42, no show-stopper problems are expected. At this point we can still revert if insurmountable problems appear, but to do so may require a mass rebuild if the defects involve generated binaries.
 <!-- Use this text for a GCC update: -->
 <!-- Not needed in F[X is odd] because GCC is not being updated. -->
-* Contingency mechanism for gcc: If gcc X-1 proves too disruptive to compiling the distribution we could revert to gcc X-1.
+* Contingency mechanism for gcc: If gcc 14.1+ proves too disruptive to compiling the distribution we could revert to gcc 14.0.
 <!-- No comments needed because GDB updates asynchornously. -->
@@ Line 206: / Line 207: @@
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
-* Contingency deadline: Fedora mass rebuild on YYYY-MM-DD. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Contingency deadline: Fedora mass rebuild on 2024-07-17. <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? -->
 * Blocks release?
-** No, upgrading to gcc X.Y does block the release.
+** No, upgrading to gcc 14+ does block the release.
-** Yes, upgrading to gcc X.0 does block the release. [TODO: Remove if this is not the first Fedora release with this gcc major]
+** Yes, upgrading to binutils 2.42 does block the release.
-** Yes, upgrading to binutils X.Y does block the release.
+** Yes, upgrading to glibc 2.40 does block the release.
-** Yes, upgrading to glibc X.Y does block the release.
+** No, upgrading to gdb 14+ does not block the release.
-** No, upgrading to gdb X.Y does not block the release.
 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 236: / Line 236: @@
 <!-- Use this text for GCC updates: -->
-See https://gcc.gnu.org/gcc-X/changes.html for the GNU Compiler Collection version X release notes.
+See https://gcc.gnu.org/gcc-14/changes.html for the GNU Compiler Collection version 14 release notes.
 <!-- Use this text for GLIBC updates: -->
-The GNU C Library version X.Y will be released at the beginning of August/February YYYY. The current NEWS notes can be seen here as they are added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD
+The GNU C Library version 2.40 will be released at the beginning of August 2024. The current NEWS notes can be seen here as they are added: https://sourceware.org/git/?p=glibc.git;a=blob;f=NEWS;hb=HEAD
-The GNU Binary Utilities version X.Y was released August/February YYYY. The current release notes will be sent to the developer mailing list.
+The GNU Binary Utilities version 2.42 was released February 2024. The current release notes will be sent to the developer mailing list.

Search

Changes/GNUToolchainF41: Difference between revisions