Revision as of 20:31, 16 December 2024

GNU Toolchain Update (gcc 15, binutils 2.44, glibc 2.41, gdb 15+)

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee.

Summary

Update the Fedora 42 GNU Toolchain to gcc 15, binutils 2.44, glibc 2.41 and gdb 15+.

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

GNU C Compiler 15
- Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), Fortran (gfortran), D (phobos), Objective C/C++.
GNU Binary Utilities 2.44
GNU C Library 2.41
GNU Debugger 15+ (immediately available in Fedora 40 and 41 today)

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

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

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

The gdb 15+ update was 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.

Owner

Name: Carlos O'Donell

Email: carlos@redhat.com

Current status

Targeted release: Fedora Linux 42
Last updated: 2024-12-16
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] Yes. Fedora 42 has an Ada SONAME change. The SONAME bump will be coordinated in a side-tag.
[Announced]
[<will be assigned by the Wrangler> Discussion thread]
FESCo issue: <will be assigned by the Wrangler>
Tracker bug: <will be assigned by the Wrangler>
Release notes tracker: <will be assigned by the Wrangler>

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 15 (major release), before the Fedora 42 release. It will contain many new features, documented here: https://gcc.gnu.org/gcc-15/changes.html. The latest point release for gcc 15 may be included in Fedora 42, this will most probably be 15.1 or later.

The GNU Binutils version 2.44 will be released before Fedora 42; and we have already been using this version of binutils in Fedora Rawhide successfully to build the distribution. Given the present schedule for Fedora 42 we will continue to use Binutils 2.44.

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

The GNU Debugger version 15+ 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 42 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; #12504

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.41 will be noted here: https://sourceware.org/glibc/wiki/Release/2.41#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 42 cycle. The mass rebuild would ensure all packages can be built with the newer compiler and core runtimes.

Contingency Plan

Contingency mechanism glibc: If glibc 2.41 proves too disruptive to compiling the distribution we could revert to 2.40, but given that Rawhide has started tracking glibc 2.41, no show-stopper problems are expected. At this point we can still revert to upstream version 2.40 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.44 proves too distruptive to assembling and linking the distribution we could revert to 2.43, but given that Rawhide is using 2.44, 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 15 proves too disruptive to compiling the distribution we could revert to gcc 14+, but given that we are executing a mass-prebuild using COPR we expect to have advance warning of any serious problems.

Contingency deadline: Fedora mass rebuild on 2024-07-17.
Blocks release?
- Yes, upgrading to gcc 15 does block the release.
- Yes, upgrading to binutils 2.44 does block the release.
- Yes, upgrading to glibc 2.41 does block the release.
- No, upgrading to gdb 15+ 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-15/changes.html for the GNU Compiler Collection version 15 release notes.

The GNU C Library version 2.41 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.44 will be released in February 2024. The current release notes will be sent to the developer mailing list.

The GNU Debugger version 15 was released September 2024. The release notes can be seen here: https://inbox.sourceware.org/gdb-announce/20240929090637.DCD1780649@takamaka.gnat.com/T/#u

@@ 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 -->
+= GNU Toolchain Update (gcc 15, binutils 2.44, glibc 2.41, gdb 15+) =
-= GNU Toolchain Update (gcc 15, binutils 2.44, glibc 2.41, gdb 15+) <!-- The name of your change proposal --> =
+{{Change_Proposal_Banner}}
 == 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 42 GNU Toolchain to gcc 15, binutils 2.44, glibc 2.41 and gdb 15+.
@@ Line 23: / Line 24: @@
 == Owner ==
-<!--
-For change proposals to qualify as self-contained, owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.
-This should link to your home wiki page so we know who you are.
--->
 * Name: [[User:codonell|Carlos O'Donell]]
-<!-- Include you email address that you can be reached should people want to contact you about helping with your change, status is requested, or technical issues need to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->
 * Email: carlos@redhat.com
-<!--- UNCOMMENT only for Changes with assigned Shepherd (by FESCo)
-* FESCo shepherd: [[User:FASAccountName| Shehperd name]] <email address>
--->
 == Current status ==
@@ Line 63: / Line 59: @@
 == Detailed Description ==
-<!-- Expand on the summary, if appropriate.  A couple sentences suffices to explain the goal, but the more details you can provide the better. -->
 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.
@@ Line 80: / Line 75: @@
 == Benefit to Fedora ==
-<!-- What is the benefit to the distribution?  Will the software we generate be improved? How will the process of creating Fedora releases be improved?
-      Be sure to include the following areas if relevant:
-      If this is a major capability update, what has changed?
-           For example: This change introduces Python 5 that runs without the Global Interpreter Lock and is fully multithreaded.
-      If this is a new functionality, what capabilities does it bring?
-           For example: This change allows package upgrades to be performed automatically and rolled-back at will.
-      Does this improve some specific package or set of packages?
-           For example: This change modifies a package to use a different language stack that reduces install size by removing dependencies.
-      Does this improve specific Spins or Editions?
-           For example: This change modifies the default install of Fedora Workstation to be more in line with the base install of Fedora Server.
-      Does this make the distribution more efficient?
-           For example: This change replaces thousands of individual %post scriptlets in packages with one script that runs at the end.
-      Is this an improvement to maintainer processes?
-           For example: Gating Fedora packages on automatic QA tests will make rawhide more stable and allow changes to be implemented more smoothly.
-      Is this an improvement targeted as specific contributors?
-           For example: Ensuring that a minimal set of tools required for contribution to Fedora are installed by default eases the onboarding of new contributors.
-     When a Change has multiple benefits, it's better to list them all.
-     Consider these Change pages from previous editions as inspiration:
-     https://fedoraproject.org/wiki/Changes/Annobin (low-level and technical, invisible to users)
-     https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo (low-level, but visible to advanced users)
-     https://fedoraproject.org/wiki/Changes/VirtualBox_Guest_Integration (primarily a UX change)
-     https://fedoraproject.org/wiki/Changes/NoMoreAlpha (an improvement to distro processes)
-     https://fedoraproject.org/wiki/Changes/perl5.26 (major upgrade to a popular software stack, visible to users of that stack)
--->
 Stays up to date with latest features, improvements, security and bug fixes from gcc, glibc, binutils, and gdb upstream.
@@ Line 115: / Line 83: @@
 * 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 42 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?-->
+* 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; [https://pagure.io/releng/issue/12504 #12504]
-<!-- 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 -->
-* Policies and guidelines: N/A (not needed for this Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Policies and guidelines: N/A (not needed for this Change)
 <!-- Do the packaging guidelines or other documents need to be updated for this feature?  If so, does it need to happen before or after the implementation is done?  If a FPC ticket exists, add a link here. Please submit a pull request with the proposed changes before submitting your Change proposal. -->
 * Trademark approval: N/A (not needed for this Change)
-<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. -->
 * Alignment with Objectives: N/A
-<!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider -->
 == Upgrade/compatibility impact ==
-<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? -->
 The compiler, the static linker and the the library are backwards compatible with the previous version of Fedora.
@@ Line 138: / Line 104: @@
 <!-- Some source changes may be required for gcc X rebase: https://gcc.gnu.org/gcc-X/changes.html -->
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 Any source level changes required for glibc 2.41 will be noted here: https://sourceware.org/glibc/wiki/Release/2.41#Packaging_Changes
 == How To Test ==
-<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done.  If it needs to be tested with different hardware or software configurations, indicate them.  The more specific you can be, the better the community testing can be.
-Remember that you are writing this how to for interested testers to use to check out your change implementation - documenting what you do for testing is OK, but it's much better to document what *I* can do to test your change.
-A good "how to test" should answer these four questions:
-. What special hardware / data / etc. is needed (if any)?
-. How do I prepare my system to test this change? What packages
-need to be installed, config files edited, etc.?
-. What specific actions do I perform to check that the change is
-working like it's supposed to?
-. What are the expected results of those actions?
--->
 <!-- Use this text for a GCC update: -->
@@ Line 169: / Line 122: @@
 == User Experience ==
-<!-- If this change proposal is noticeable by users, how will their experiences change as a result?
- This section partially overlaps with the Benefit to Fedora section above. This section should be primarily about the User Experience, written in a way that does not assume deep technical knowledge. More detailed technical description should be left for the Benefit to Fedora section.
- Describe what Users will see or notice, for example:
-  - Packages are compressed more efficiently, making downloads and upgrades faster by 10%.
-  - Kerberos tickets can be renewed automatically. Users will now have to authenticate less and become more productive. Credential management improvements mean a user can start their work day with a single sign on and not have to pause for reauthentication during their entire day.
- - Libreoffice is one of the most commonly installed applications on Fedora and it is now available by default to help users "hit the ground running".
- - Green has been scientifically proven to be the most relaxing color. The move to a default background color of green with green text will result in Fedora users being the most relaxed users of any operating system.
--->
 <!-- TODO: Talk about any new GNU Toolchain user experience updates. -->
@@ Line 184: / Line 127: @@
 == 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 42 cycle. The mass rebuild would ensure all packages can be built with the newer compiler and core runtimes.
 == 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 2.41 proves too disruptive to compiling the distribution we could revert to 2.40, but given that Rawhide has started tracking glibc 2.41, no show-stopper problems are expected.  At this point we can still revert to upstream version 2.40 if insurmountable problems appear, but to do so may require a mass rebuild to remove new symbols from the ABI/API.
@@ Line 210: / Line 152: @@
 ** No, upgrading to gdb 15+ does not block the release.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == Documentation ==
-<!-- Is there upstream documentation on this change, or notes you have written yourself?  Link to that material here so other interested developers can get involved. -->
 The gcc manual contains the documentation for the release and doesn't need any more additional work.
@@ Line 221: / Line 162: @@
 The gdb manual contains the documentation for the release and doesn't need any more additional work.
-<!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 == Release Notes ==
-<!-- The Fedora Release Notes inform end-users about what is new in the release.  Examples of past release notes are here: http://docs.fedoraproject.org/release-notes/ -->
-<!-- The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns.  If there are any such changes involved in this change, indicate them here.  A link to upstream documentation will often satisfy this need.  This information forms the basis of the release notes edited by the documentation team and shipped with the release.
-Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze.
--->
 <!-- Use this text for GCC updates: -->

Search

Changes/GNUToolchainF42: Difference between revisions