Revision as of 08:44, 19 December 2023

Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "view source" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.

Guidance
For details on how to fill out this form, see the documentation.

Report issues
To report an issue with this template, file an issue in the pgm_docs repo.

LLVM 18

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 all llvm sub-projects in Fedora Linux to version 18.

Owner

Name: Tom Stellard
Email: <tstellar@redhat.com>

Current status

Targeted release: Fedora Linux 40
Last updated: 2023-12-19
[<will be assigned by the Wrangler> devel 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

All llvm sub-projects in Fedora will be updated to version 18, and there will be a soname version change for the llvm libraries. Compatibility packages clang17, llvm17, and lld17 will be added to ensure that packages that currently depend on clang and llvm version 17 libraries will continue to work. These older compatibility packages will be orphaned:

llvm14
llvm15
llvm16
clang14
clang15
clang16
lld14
lld15
lld16

Other notable changes:

clang will emit DWARF-5 by default instead of DWARF-4. This matches the upstream default. We have been using DWARF-4 as the default for the last few releases due to: https://bugzilla.redhat.com/show_bug.cgi?id=2064052
The compatibility packages will now include the same content as the main package. In previous releases, the compatibility packages contained only libraries and headers, and the binaries and other content was stripped out. These packages will be supported for use as dependencies for other RPM packages, but not for general purpose usage by end users. Fedora users should use Clang/LLVM 18.
We will be enabling Fat LTO in redhat-rpm-config if this feature is complete in time for the upstream LLVM 18 release.

LLVM Build Schedule

Important Dates

Jan 26: Upstream: 18.0.0-rc1 Release
Feb 6: Fedora: f40 branch created
Feb 6: Upstream: 18.0.0-rc2 Release
Feb 20: Fedora: f40 Beta Freeze
Feb 20: Upstream: 18.0.0-rc3 Release
Mar 5: Upstream: 18.0.0 Release
Apr 2: Fedora: f40 Final Freeze

Plan

Build LLVM 18.0.0-rc1 in COPR.
Build LLVM 18.0.0-rc1 into a rawhide side-tag in Koji.
Build LLVM 18.0.0-rc1 into a f39 side-tag in Koji.
Build LLVM 18.0.0-rc2 into a rawhide side-tag in Koji.
Build LLVM 18.0.0-rc2 into a f39 side-tag in Koji.
Build LLVM 18.0.0-rc3 into a rawhide side-tag in Koji
Build LLVM 18.0.0-rc3 into a f39 side-tag in Koji
Push F39 Bodhi Update with 18.0.0-rc3 (or 18.0.0-rc2 if -rc3 is not ready) as a Beta Freeze exception.
Continue building new release candidates and pushing them to stable until the Final Freeze.

We are not planning to push 18.0.0-rc1 into rawhide because the library ABI is not stabilized at that point. Typically, the ABI stabilizes after -rc3, but there are no guarantees from upstream about this. Given the history of minimal ABI changes after -rc3, we feel like it's safe to push -rc3 into rawhide. The worst case scenario would be an ABI change -rc4 or the final release that we force us to patch LLVM to maintain compatibility with the -rc3 ABI. This scenario would not require rebuilding LLVM library users in Fedora, so this would not require much extra work from our team.

Updates after 18.0.0-rc3 will generally be very small and can be done after the Final Freeze is over. If we are late packaging release candidates after -rc3 or the final release, we will not ask for a Final Freeze exception, unless they contain a fix for a critical release blocking bug.

Feedback

Benefit to Fedora

New features and bug fixes provided by the latest version of LLVM.

Scope

Proposal owners:
- Review existing llvm and clang compatibility packages and orphan any packages that are no longer used.
- Do scratch builds of Fedora packages that depend on llvm and report issues to package maintainer.

Other developers:
- Fix build issues found with LLVM-18 or switch their package to use the llvm17 compat libs. The LLVM team no longer plans to block Bodhi updates on dependent packages that fail to build or run with LLVM-18. There should be around 6-8 weeks between when -rc1 lands in koji and the Final Freeze for package maintainers to fix issues uncovered with the LLVM-18 update.

Release engineering: #11845

Policies and guidelines: N/A (not needed for this Change)

Trademark approval: N/A (not needed for this Change)

Alignment with Community Initiatives:

Upgrade/compatibility impact

This change should not impact upgrades.

How To Test

The CI tests for the llvm sub-packages in Fedora will be used to catch regressions that might be potentially introduced by the update to LLVM 18.

User Experience

Dependencies

Packages that depend on one of the llvm packages will need to be updated to work with LLVM18 or will need to switch to using one of the llvm17 compat packages.

Contingency Plan

Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)

If there are major problems with LLVM 18, the compatibility package provide a way for other packages to continue using LLVM 17.

Contingency deadline: Final Freeze
Blocks release? No

Documentation

LLVM sub-projects in Fedora have been updated to version 18:

llvm
clang
lld
lldb
compiler-rt
libomp
llvm-test-suite
libcxx
python-lit
flang
mlir
polly
libclc
llvm-bolt

Release Notes

@@ Line 13: / Line 13: @@
 == 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 all llvm sub-projects in Fedora Linux to version 17.
+Update all llvm sub-projects in Fedora Linux to version 18.
 == Owner ==
 <!--
@@ Line 74: / Line 74: @@
 ====Important Dates====
-* Jan  27: Upstream: 18.0.0-rc1 Release
+* Jan  26: Upstream: 18.0.0-rc1 Release
 * Feb   6: Fedora: f40 branch created
 * Feb   6: Upstream: 18.0.0-rc2 Release
@@ Line 91: / Line 91: @@
 # Build LLVM 18.0.0-rc3 into a rawhide side-tag in Koji
 # Build LLVM 18.0.0-rc3 into a f39 side-tag in Koji
-# Push F39 Bodhi Update with 18.0.0-rc3 (or 17.0.0-rc2 if -rc3 is not ready) as a Beta Freeze exception.
+# Push F39 Bodhi Update with 18.0.0-rc3 (or 18.0.0-rc2 if -rc3 is not ready) as a Beta Freeze exception.
 # Continue building new release candidates and pushing them to stable until the Final Freeze.
-We are not planning to push 18.0.0-rc1 into rawhide because the library ABI is not stabilized at that point. Typically, the ABI stabilizes after -rc3, but there are no guarantees from upstream about this.  Given the history of minimal ABI changes after -rc3, we feel like it's safe to push -rc3 into rawhide.  The worst case scenario would be an ABI change -rc4 or the fianl release that we force us to patch LLVM to maintain compatibility with the -rc3 ABI.  This scenario would not require rebuilding LLVM library users in Fedora, so this would not require much extra work from our team.
+We are not planning to push 18.0.0-rc1 into rawhide because the library ABI is not stabilized at that point. Typically, the ABI stabilizes after -rc3, but there are no guarantees from upstream about this.  Given the history of minimal ABI changes after -rc3, we feel like it's safe to push -rc3 into rawhide.  The worst case scenario would be an ABI change -rc4 or the final release that we force us to patch LLVM to maintain compatibility with the -rc3 ABI.  This scenario would not require rebuilding LLVM library users in Fedora, so this would not require much extra work from our team.
-Updates after 17.0.0-rc3 will generally be very small and can be done after the Final Freeze is over.  If we are late packaging release candidates after -rc3 or the final release, we will not ask for a Final Freeze exception, unless they contain a fix for a critical release blocking bug.
+Updates after 18.0.0-rc3 will generally be very small and can be done after the Final Freeze is over.  If we are late packaging release candidates after -rc3 or the final release, we will not ask for a Final Freeze exception, unless they contain a fix for a critical release blocking bug.
 == Feedback ==
@@ Line 136: / Line 136: @@
 ** Review existing llvm and clang compatibility packages and orphan any packages that are no longer used.
 ** Do scratch builds of Fedora packages that depend on llvm and report issues to package maintainer.
 * Other developers: <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- 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?-->
-** Fix build issues found with LLVM-18 or switch their package to use the llvm16 compat libs.  The LLVM team no longer plans to block Bodhi updates on dependent packages that fail to build or run with LLVM-18.  There should be around 6-8 weeks between when -rc1 lands in koji and the Final Freeze for package maintainers to fix issues uncovered with the LLVM-18 update.
+** Fix build issues found with LLVM-18 or switch their package to use the llvm17 compat libs.  The LLVM team no longer plans to block Bodhi updates on dependent packages that fail to build or run with LLVM-18.  There should be around 6-8 weeks between when -rc1 lands in koji and the Final Freeze for package maintainers to fix issues uncovered with the LLVM-18 update.
 * Release engineering: [https://pagure.io/releng/issues/11845 #11845] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
@@ Line 201: / Line 200: @@
 <!-- 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: (What to do?  Who will do it?) N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-If there are major problems with LLVM 17, the compatibility package provide a way for other packages to continue using LLVM 16.
+If there are major problems with LLVM 18, the compatibility package provide a way for other packages to continue using LLVM 17.
 <!-- When is the last time the contingency mechanism can be put in place?  This will typically be the beta freeze. -->
 * Contingency deadline: Final Freeze  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->

Search

Changes/LLVM-18: Difference between revisions