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 X.Y, binutils X.Y, glibc X.Y, gdb X.Y)
Summary
Update the Fedora XX GNU Toolchain to gcc X.Y, binutils X.Y, glibc X.Y and gdb X.Y.
The set of core GNU Toolchain packages for Fedora 3XX are as follows:
- GNU C Compiler X.Y
- Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), Fortran (gfortran), D (phobos), Objective C/C++.
- GNU Binary Utilities X.Y
- GNU C Library X.Y
- GNU Debugger X.Y (immediately available in Fedora XX)
The gcc X.Y 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 glibc X.Y 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.
Owner
- Name: Carlos O'Donell
- Email: carlos@redhat.com
Current status
- Targeted release: Fedora Linux XX
- Last updated: 2024-01-16
- devel thread
- 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)
- Did we rebuild the packages in the side-tag before merging?
- FESCo issue: #XX
- Tracker bug: #XX
- Release notes tracker: #XX
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 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 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 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 Debugger version X.Y 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 XX 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; #XX
- 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 X.Y will be noted here: https://sourceware.org/glibc/wiki/Release/X.Y#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 XX 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 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 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 for gcc: If gcc X-1 proves too disruptive to compiling the distribution we could revert to gcc X-1.
- Contingency deadline: Fedora mass rebuild on YYYY-MM-DD.
- Blocks release?
- No, upgrading to gcc X.Y 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 X.Y does block the release.
- Yes, upgrading to glibc X.Y does block the release.
- No, upgrading to gdb X.Y 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-X/changes.html for the GNU Compiler Collection version X release notes.
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 Binary Utilities version X.Y was released August/February YYYY. The current release notes will be sent to the developer mailing list.