public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Nikita Popov <npopov@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/llvm] f45: Rebase patch for LLVM 24
Date: Wed, 16 Sep 2026 12:28:35 GMT [thread overview]
Message-ID: <178956171502.1.7180975213878307373.rpms-llvm-5bb893ddf69b@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/llvm
Branch : f45
Commit : 5bb893ddf69b960c0105b2508b9ee80467e28738
Author : Nikita Popov <npopov@redhat.com>
Date : 2026-09-15T10:23:05+02:00
Stats : +64/-31 in 4 file(s)
URL : https://src.fedoraproject.org/rpms/llvm/c/5bb893ddf69b960c0105b2508b9ee80467e28738?branch=f45
Log:
Rebase patch for LLVM 24
---
diff --git a/0001-21-Workaround-a-bug-in-ORC-on-ppc64le.patch b/0001-21-Workaround-a-bug-in-ORC-on-ppc64le.patch
new file mode 100644
index 0000000..af236a1
--- /dev/null
+++ b/0001-21-Workaround-a-bug-in-ORC-on-ppc64le.patch
@@ -0,0 +1,30 @@
+From a2449cee8c995b56f1892502aab3dfad3d6f3ca1 Mon Sep 17 00:00:00 2001
+From: Tulio Magno Quites Machado Filho <tuliom@redhat.com>
+Date: Fri, 8 Sep 2023 11:45:34 -0300
+Subject: [PATCH] Workaround a bug in ORC on ppc64le
+
+The Jit code appears to be returning the wrong printf symbol on ppc64le
+after the transition of the default long double to IEEE 128-bit floating
+point.
+---
+ clang/unittests/Interpreter/InterpreterTest.cpp | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/clang/unittests/Interpreter/InterpreterTest.cpp b/clang/unittests/Interpreter/InterpreterTest.cpp
+index abb8e6377aab..7b6697ebc6ed 100644
+--- a/clang/unittests/Interpreter/InterpreterTest.cpp
++++ b/clang/unittests/Interpreter/InterpreterTest.cpp
+@@ -243,7 +243,9 @@ TEST(IncrementalProcessing, FindMangledNameSymbol) {
+ EXPECT_FALSE(!Addr);
+
+ // FIXME: Re-enable when we investigate the way we handle dllimports on Win.
+-#ifndef _WIN32
++ // FIXME: The printf symbol returned from the Jit may not be correct on
++ // ppc64le when the default long double is IEEE 128-bit fp.
++#if !defined _WIN32 && !(defined __PPC64__ && defined __LITTLE_ENDIAN__)
+ EXPECT_EQ((uintptr_t)&printf, Addr->getValue());
+ #endif // _WIN32
+ }
+--
+2.41.0
+
diff --git a/0001-24-Workaround-a-bug-in-ORC-on-ppc64le.patch b/0001-24-Workaround-a-bug-in-ORC-on-ppc64le.patch
new file mode 100644
index 0000000..d0a4e41
--- /dev/null
+++ b/0001-24-Workaround-a-bug-in-ORC-on-ppc64le.patch
@@ -0,0 +1,30 @@
+From 0ce01c3985bb7b37c4070e420f9ca404f077dde9 Mon Sep 17 00:00:00 2001
+From: Tulio Magno Quites Machado Filho <tuliom@redhat.com>
+Date: Tue, 15 Sep 2026 10:01:20 +0200
+Subject: [PATCH] Workaround a bug in ORC on ppc64le
+
+The Jit code appears to be returning the wrong printf symbol on ppc64le
+after the transition of the default long double to IEEE 128-bit floating
+point.
+---
+ clang/unittests/Interpreter/InterpreterTest.cpp | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/clang/unittests/Interpreter/InterpreterTest.cpp b/clang/unittests/Interpreter/InterpreterTest.cpp
+index 3becd00c1282..8c9d63dccac8 100644
+--- a/clang/unittests/Interpreter/InterpreterTest.cpp
++++ b/clang/unittests/Interpreter/InterpreterTest.cpp
+@@ -284,7 +284,9 @@ TEST_F(InterpreterTest, FindMangledNameSymbol) {
+ EXPECT_FALSE(!Addr);
+
+ // FIXME: Re-enable when we investigate the way we handle dllimports on Win.
+-#ifndef _WIN32
++ // FIXME: The printf symbol returned from the Jit may not be correct on
++ // ppc64le when the default long double is IEEE 128-bit fp.
++#if !defined _WIN32 && !(defined __PPC64__ && defined __LITTLE_ENDIAN__)
+ EXPECT_EQ(llvm::orc::ExecutorAddr::fromPtr(&printf), *Addr);
+ #endif // _WIN32
+ }
+--
+2.55.0
+
diff --git a/0001-Workaround-a-bug-in-ORC-on-ppc64le.patch b/0001-Workaround-a-bug-in-ORC-on-ppc64le.patch
deleted file mode 100644
index af236a1..0000000
--- a/0001-Workaround-a-bug-in-ORC-on-ppc64le.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From a2449cee8c995b56f1892502aab3dfad3d6f3ca1 Mon Sep 17 00:00:00 2001
-From: Tulio Magno Quites Machado Filho <tuliom@redhat.com>
-Date: Fri, 8 Sep 2023 11:45:34 -0300
-Subject: [PATCH] Workaround a bug in ORC on ppc64le
-
-The Jit code appears to be returning the wrong printf symbol on ppc64le
-after the transition of the default long double to IEEE 128-bit floating
-point.
----
- clang/unittests/Interpreter/InterpreterTest.cpp | 4 +++-
- 1 file changed, 3 insertions(+), 1 deletion(-)
-
-diff --git a/clang/unittests/Interpreter/InterpreterTest.cpp b/clang/unittests/Interpreter/InterpreterTest.cpp
-index abb8e6377aab..7b6697ebc6ed 100644
---- a/clang/unittests/Interpreter/InterpreterTest.cpp
-+++ b/clang/unittests/Interpreter/InterpreterTest.cpp
-@@ -243,7 +243,9 @@ TEST(IncrementalProcessing, FindMangledNameSymbol) {
- EXPECT_FALSE(!Addr);
-
- // FIXME: Re-enable when we investigate the way we handle dllimports on Win.
--#ifndef _WIN32
-+ // FIXME: The printf symbol returned from the Jit may not be correct on
-+ // ppc64le when the default long double is IEEE 128-bit fp.
-+#if !defined _WIN32 && !(defined __PPC64__ && defined __LITTLE_ENDIAN__)
- EXPECT_EQ((uintptr_t)&printf, Addr->getValue());
- #endif // _WIN32
- }
---
-2.41.0
-
diff --git a/llvm.spec b/llvm.spec
index 6976e90..5c2786e 100644
--- a/llvm.spec
+++ b/llvm.spec
@@ -553,7 +553,10 @@ Patch102: 0003-PATCH-clang-Don-t-install-static-libraries.patch
# Workaround a bug in ORC on ppc64le.
# More info is available here: https://reviews.llvm.org/D159115#4641826
-Patch103: 0001-Workaround-a-bug-in-ORC-on-ppc64le.patch
+Patch2107: 0001-21-Workaround-a-bug-in-ORC-on-ppc64le.patch
+Patch2218: 0001-21-Workaround-a-bug-in-ORC-on-ppc64le.patch
+Patch2303: 0001-21-Workaround-a-bug-in-ORC-on-ppc64le.patch
+Patch2402: 0001-24-Workaround-a-bug-in-ORC-on-ppc64le.patch
# With the introduction of --gcc-include-dir in the clang config file,
# this might no longer be needed.
reply other threads:[~2026-09-16 12:28 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=178956171502.1.7180975213878307373.rpms-llvm-5bb893ddf69b@fedoraproject.org \
--to=npopov@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