Bug 2427441 - Changes/GNUToolchainF44
Summary: Changes/GNUToolchainF44
Keywords:
Status: ON_QA
Alias: None
Product: Fedora
Classification: Fedora
Component: Changes Tracking
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: F44Changes
TreeView+ depends on / blocked
 
Reported: 2026-01-06 17:51 UTC by Allison King
Modified: 2026-03-12 21:53 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:
fedora-admin-xmlrpc: mirror+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker FC-2895 0 None None None 2026-01-06 17:57:40 UTC

Description Allison King 2026-01-06 17:51:19 UTC
This is a tracking bug for Change: Changes/GNUToolchainF44
For more details, see: https://fedoraproject.org/wiki/Changes/GNUToolchainF44

<!-- 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 44 GNU Toolchain to gcc 16.1, binutils 2.46, glibc 2.43 and gdb 16.3.

'''The update includes raising the ISA baseline in redhat-rpm-config for IBM zSeries from z13

If you encounter a bug related to this Change, please do not comment here. Instead create a new bug and set it to block this bug.

Comment 1 Allison King 2026-02-03 19:37:31 UTC
Hi codonell, how goes this change for F44? The testable deadline is today, February 03, 2026, and changes need to be in good shape at this point https://docs.fedoraproject.org/en-US/program_management/changes_policy/#_change_process_milestones

Please let me know if you need to defer this to F45, otherwise if you're good to go for the change to be ready to meet the testable requirements, please update the status of the tracker bug to MODIFIED.

Thanks!

Comment 2 Carlos O'Donell 2026-02-04 17:41:37 UTC
(In reply to Allison King from comment #1)
> Hi codonell, how goes this change for F44? The testable deadline is today,
> February 03, 2026, and changes need to be in good shape at this point
> https://docs.fedoraproject.org/en-US/program_management/changes_policy/
> #_change_process_milestones
> 
> Please let me know if you need to defer this to F45, otherwise if you're
> good to go for the change to be ready to meet the testable requirements,
> please update the status of the tracker bug to MODIFIED.

We are done.

GCC is done:
https://bodhi.fedoraproject.org/updates/FEDORA-2026-5eb45e8875

BINTUILS is done:
https://bodhi.fedoraproject.org/updates/FEDORA-2026-6aa8e4b1bc

GLIBC is done:
https://bodhi.fedoraproject.org/updates/FEDORA-2026-22092ea559
- And moved to the stable release branch for ABI assurances.

GDB is done:
https://bodhi.fedoraproject.org/updates/FEDORA-2026-f4d94acce7
- Updated to the 17 release.

Comment 3 Zbigniew Jędrzejewski-Szmek 2026-02-10 10:42:56 UTC
The Change page lists 16.1, but the update has gcc-16.0.1. Can you clarify and/or update the Change page to match?

Comment 4 Carlos O'Donell 2026-02-27 18:41:39 UTC
(In reply to Zbigniew Jędrzejewski-Szmek from comment #3)
> The Change page lists 16.1, but the update has gcc-16.0.1. Can you clarify
> and/or update the Change page to match?

Initially GCC 16.0 (Stage 4, RC) is included, but as noted in the system-wide change request:
~~~
The latest point release for gcc 16 will be included in Fedora 44, this will most probably be 16.1 or 16.2. 
~~~

In March-April timeframe the compiler will be rebased to the latest point release. This rebase should be minor and include discovered bug fixes, but gives us a final release for Fedora 44.

As-is the system-wide change request is correct, but describes the *final* state (with versions) of the change.

In this case we complete "Code complete (testable) deadline" in that we have tested GCC 16.0 (Stage 4, RC), but will end up collecting more bug fixes via GCC 16.1.


Note You need to log in before you can comment on or make changes to this bug.