Revision as of 21:17, 21 November 2022

LLVM 16

Summary

Update all llvm sub-projects in Fedora Linux to version 16.

Owner

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

Current status

Targeted release: Fedora Linux 38
Last updated: 2022-11-21
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 16, and there will be a soname version change for the llvm libraries. Compatibility packages clang15 and llvm15 will be added to ensure that packages that currently depend on clang and llvm version 15 libraries will continue to work.

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.
- Build release candidates into @fedora-llvm-team/llvm16 COPR.
- Build final release (March 2023) into Rawhide and F38 branches.

Other developers:
- Maintainers of packages that depend on clang-libs or llvm-libs will need to update their spec files to depend on the clang15 and llvm15 compatibility packages if they want to rebuild their package and it does not work with LLVM 16 yet. The key point here is that spec file changes are only needed if a package is going to be rebuilt after LLVM 16 is added to Fedora. The compatibility packages will ensure that already built packages continue to work.

Release engineering: #Releng issue number

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

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

Alignment with Objectives:

Upgrade/compatibility impact

This change should not impact upgradeability.

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 15.

User Experience

Dependencies

This change can be made without updating any other packages. However, as mention before, packages that need to use LLVM 14 will need to update their spec file on their first rebuild after this change.

Contingency Plan

Contingency mechanism: (What to do? Who will do it?) Contingency mechanism: (What to do? Who will do it?): If there are major problems with LLVM 15, the compatibility package provide a way for other packages to continue using LLVM 14.
Contingency deadline: Final Freeze
Blocks release? No

Documentation

Release notes will be added for this change.

Release Notes

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

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

@@ Line 90: / Line 90: @@
 <!-- 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: [https://pagure.io/releng/issues/10820 #10820] <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Release engineering: [https://pagure.io/releng/issues #Releng issue number]  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
 <!-- 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 -->

Search

Changes/LLVM-16: Difference between revisions