(Created page with "<!-- 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 14+, binutils 2.42+, glibc 2.40, gdb 14+) <!-- 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 mo...") |
No edit summary |
||
| Line 9: | Line 9: | ||
<!-- 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?". --> | <!-- 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 | 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 41 are as follows: | The set of core GNU Toolchain packages for Fedora 41 are as follows: | ||
* GNU C Compiler | * GNU C Compiler 15 | ||
** Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), Fortran (gfortran), D (phobos), Objective C/C++. | ** Associated runtimes for C++ (libstdc++), Go (gccgo), OpenMP (gomp), Fortran (gfortran), D (phobos), Objective C/C++. | ||
* GNU Binary Utilities 2. | * GNU Binary Utilities 2.44 | ||
* GNU C Library 2. | * GNU C Library 2.41 | ||
* GNU Debugger | * GNU Debugger 15+ (immediately available in Fedora 40) | ||
The gcc | The gcc 15 change will be tracked in this top-level GNU Toolchain system-wide update. | ||
The binutils 2. | The binutils 2.44 change will be tracked in this top-level GNU Toolchain system-wide update. | ||
The glibc 2. | The glibc 2.41 change will be tracked in this top-level GNU Toolchain system-wide update. | ||
The gdb | 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 == | == Owner == | ||
| Line 50: | Line 50: | ||
[[Category:SystemWideChange]] | [[Category:SystemWideChange]] | ||
* Targeted release: [[Releases/ | * Targeted release: [[Releases/42 | Fedora Linux 42 ]] | ||
* Last updated: <!-- this is an automatic macro — you don't need to change this line --> {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}} | * 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 | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
| Line 58: | Line 58: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* Updated redhat-rpm-config: [] (TODO: Check if redhat-rpm-config needs updating for the new toolchain) | * 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? | ** Are config.guess and config.sub up to date from upstream? | ||
* GCC Ada SONAME bump: [x] | * GCC Ada SONAME bump: [x] Yes. Fedora 42 has an Ada SONAME change. The SONAME bump will be coordinated in a side-tag. | ||
* Tracker bug: | * [Announced] | ||
* Release notes tracker: | * [<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 == | == Detailed Description == | ||
| Line 73: | Line 73: | ||
<!-- Use this text for a GCC update: --> | <!-- Use this text for a GCC update: --> | ||
The GNU Compiler Collection is expected to release version | 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: --> | <!-- Use this text for a BINUTILS update: --> | ||
The GNU Binutils version 2. | 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: --> | <!-- Use this text for a GLIBC update: --> | ||
The GNU C Library version 2. | 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: --> | <!-- Use this text for a GDB update: --> | ||
The GNU Debugger version | The GNU Debugger version 15+ has already been rolled out across all Fedora releases at the same time. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 118: | Line 118: | ||
== Scope == | == 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 | * 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. <!-- 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/ | * Release engineering: A mass rebuild is strongly encouraged; [https://pagure.io/releng/issue/XXXX #xxxx] | ||
<!-- 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. | <!-- 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 --> | 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 144: | Line 144: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
Any source level changes required for glibc 2. | 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 == | == How To Test == | ||
| Line 190: | Line 190: | ||
== Dependencies == | == 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)? --> | <!-- 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 | 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 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. --> | <!-- 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. | * 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. | * 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: --> | <!-- Use this text for a GCC update: --> | ||
<!-- Not needed in F[X is odd] because GCC is not being updated. --> | <!-- Not needed in F[X is odd] because GCC is not being updated. --> | ||
* Contingency mechanism for gcc: If gcc | * 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. --> | <!-- No comments needed because GDB updates asynchornously. --> | ||
| Line 210: | Line 210: | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? | ||
** | ** Yes, upgrading to gcc 15 does block the release. | ||
** Yes, upgrading to binutils 2. | ** Yes, upgrading to binutils 2.44 does block the release. | ||
** Yes, upgrading to glibc 2. | ** Yes, upgrading to glibc 2.41 does block the release. | ||
** No, upgrading to gdb | ** No, upgrading to gdb 15+ does not block the release. | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
| Line 236: | Line 236: | ||
<!-- Use this text for GCC updates: --> | <!-- Use this text for GCC updates: --> | ||
See https://gcc.gnu.org/gcc- | See https://gcc.gnu.org/gcc-15/changes.html for the GNU Compiler Collection version 14 release notes. | ||
<!-- Use this text for GLIBC updates: --> | <!-- Use this text for GLIBC updates: --> | ||
The GNU C Library version 2. | 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. | 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 | |||
Revision as of 17:03, 16 December 2024
GNU Toolchain Update (gcc 14+, binutils 2.42+, glibc 2.40, gdb 14+)
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 41 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)
The gcc 15 change will be tracked in this top-level GNU Toolchain system-wide update.
The binutils 2.44 change will be tracked in this top-level GNU Toolchain system-wide update.
The glibc 2.41 change will be tracked in this top-level GNU Toolchain system-wide update.
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; #xxxx
- 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 14 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