Wiki - https://fedoraproject.org/wiki/Changes/GNUToolchainF42) Discussion Thread - https://discussion.fedoraproject.org/t/f42-change-proposal-gnu-toolchain-update-gcc-15-binutils-2-44-glibc-2-41-gdb-15-system-wide/139839 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: [[User:codonell|Carlos O'Donell]] * Email: carlos@xxxxxxxxxx == Current status == * 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. == 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. <!-- Use this text for a GCC update: --> 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. <!-- Use this text for a BINUTILS update: --> 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. <!-- Use this text for a GLIBC update: --> 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. <!-- Use this text for a GDB update: --> 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. <!-- 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. * Release engineering: A mass rebuild is strongly encouraged; [https://pagure.io/releng/issue/12504 #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. <!-- Use this text for a GCC X update: We want to call out the CHANGES URL from upstream. --> <!-- Some source changes may be required for gcc X rebase: https://gcc.gnu.org/gcc-X/changes.html --> 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 == <!-- Use this text for a GCC update: --> 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. <!-- Use this text for a GLIBC update: --> 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. <!-- Use this text for a BINUTILS update: --> 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. <!-- Use this text for a GDB update: --> 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 == <!-- TODO: Talk about any new GNU Toolchain user experience updates. --> 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. <!-- 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 15 proves too disruptive to compiling the distribution we could revert to gcc 14+, but given that we are executing a [https://gitlab.com/fedora/packager-tools/mass-prebuild mass-prebuild] using COPR we expect to have advance warning of any serious problems. <!-- No comments needed because GDB updates asynchornously. --> * 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 == <!-- Use this text for GCC updates: --> See https://gcc.gnu.org/gcc-15/changes.html for the GNU Compiler Collection version 15 release notes. <!-- Use this text for GLIBC updates: --> 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@xxxxxxxxxxxxxxxxx/T/#u -- Aoife Moloney Fedora Operations Architect Fedora Project Matrix: @amoloney:fedora.im IRC: amoloney -- _______________________________________________ devel-announce mailing list -- devel-announce@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-announce-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
