LLVM 20
Summary
Update all llvm sub-projects in Fedora Linux to version 20.
Owner
- Name: Tom Stellard
- Email: <tstellar@redhat.com>
Current status
- Targeted release: Fedora Linux 42
- Last updated: 2024-11-22
- [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
All llvm sub-projects in Fedora will be updated to version 20, and there will be a soname version change for the llvm libraries. There will be an llvm19 compat package added to ensure that packages that currently depend on clang and llvm version 19 libraries will continue to work. Any compatibility packages we added for Fedora 42 will be retired or orphaned before the Fedora 43 branch date. As stated in the LLVM-19 change proposal, we plan to retire or orphan these older compatibility packages prior to the Fedora 42 branch date:
- llvm18
- clang18
- lld18
- compiler-rt18
- libomp18
Other notable changes:
- Retring the unversioned package name We will be retiring the llvm package and replacing it with the llvm20 package. In the future, all new versions of llvm will be distributed as a separate package with the version in its name (e.g. llvm21, llvm22, etc.)
- Merging more packages into llvm20 In Fedora 41, we merged the clang, libomp, compiler-rt, lld, python-lit, and lldb packages into the llvm srpm. For Fedora 42, we will also be merging llvm-bolt, polly, libcxx, and mlir into the llvm20 srpm.
Planned Schedule
Important Dates
Feedback
Benefit to Fedora
Scope
- Proposal owners:
- Other developers:
- 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 the Fedora Strategy:
Upgrade/compatibility impact
Early Testing (Optional)
Do you require 'QA Blueprint' support? Y/N
How To Test
User Experience
Dependencies
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
Documentation
N/A (not a System Wide Change)