public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Tulio Magno Quites Machado Filho <tuliom@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/llvm] rawhide: Disable PGO and LTO on s390x on LLVM >= 23
Date: Tue, 30 Jun 2026 14:53:15 GMT [thread overview]
Message-ID: <178283119526.1.10888986291216425764.rpms-llvm-2e159bf903f5@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/llvm
Branch : rawhide
Commit : 2e159bf903f5288d8826a03d887489254182f0b9
Author : Tulio Magno Quites Machado Filho <tuliom@redhat.com>
Date : 2026-06-30T11:52:15-03:00
Stats : +11/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/llvm/c/2e159bf903f5288d8826a03d887489254182f0b9?branch=rawhide
Log:
Disable PGO and LTO on s390x on LLVM >= 23
For the past few months, s390x builds on Fedora have been taking a
little bit more than 12 hours. Considering a 9h work day, that always
means waiting an extra business day in order to review the results of
the tests.
This long build time is causing us to adopt bad practices: we reduce
the number of testing builds we could run in order to not wait so long,
we merge PRs manually in order to not wait for another scratch build
or we simply stop testing on s390x unless that's really mandatory.
This also causes trouble for daily snapshots whose builds are reviewed
only 1 business day after the build started.
PGO has also caused issues a couple of months ago due to the high disk
usage. s390x Koji builders have 134GiB of storage and LLVM builds are
getting close to that storage usage.
CentOS and RHEL are not impacted by this, though. Their s390x builders
are larger and they also build less features than Fedora. However, in
order to benefit from the tests run on Fedora, this commit disables PGO
and LTO on s390x on CentOS and RHEL too.
---
diff --git a/llvm.spec b/llvm.spec
index e241abc..31dc3ac 100644
--- a/llvm.spec
+++ b/llvm.spec
@@ -188,12 +188,18 @@ end
%ifarch %{ix86}
%bcond_with pgo
%else
+# Disable PGO on s390x temporarily in order to reduce LLVM build time and
+# disk usage.
+%if %{maj_ver} >= 23 && "%{_arch}" == "s390x"
+%bcond_with pgo
+%else
%if 0%{?fedora} >= 43 || 0%{?rhel} >= 9
%bcond_without pgo
%else
%bcond_with pgo
%endif
%endif
+%endif
# Sanity checks for PGO and bootstrapping
#----------------------------------------
@@ -209,6 +215,10 @@ end
%ifarch %ix86 riscv64
%bcond_with lto_build
%else
+# Disable LTO on s390x in order to reduce LLVM build time.
+%if %{maj_ver} >= 23 && "%{_arch}" == "s390x"
+%bcond_with pgo
+%else
%if %{defined rhel} && 0%{?rhel} <= 8
# LTO builds got enabled on Fedora and RHEL >= 9 only.
%bcond_with lto_build
@@ -216,6 +226,7 @@ end
%bcond_without lto_build
%endif
%endif
+%endif
%if 0%{?rhel} == 8
reply other threads:[~2026-06-30 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178283119526.1.10888986291216425764.rpms-llvm-2e159bf903f5@fedoraproject.org \
--to=tuliom@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox