Changes/LLVM-20

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 20

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

Owner

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

Current status

• Targeted release: Fedora Linux 42
• Last updated: 2024-11-23
• [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. We will also 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.)

There will be a soname version change for the llvm libraries, and 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 are going to be moving to a python-style package naming scheme where each new major version of llvm will be it's own package with the version number embedded in the name (e.g. llvm20).

The install prefix for all new llvm packages will be /usr/lib64/llvm$VERSION/ instead of /usr/. There will be one version of llvm designated as the main version. In the main version, there will be symlinks for each binary and library added to /usr/ which point to the corresponding binary in /usr/lib64/llvm$VERSION/

The main version will have an SRPM name of llvm$VERSION, but the binary RPMs will be unversioned (e.g. llvm instead of llvm$VERSION), and they will have provides llvm(major) = $VERSION, which will allow any packages that depend on LLVM to pin their dependencies to a specific version.

The goal of this change is to reduce the differences between the compat and non-compat versions so that it it easier for packages that depend on llvm to switch between the two.

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

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:

Early Testing (Optional)

Do you require 'QA Blueprint' support? Y/N

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)