From: "Zoltán Böszörményi" <zboszor@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>,
"Quentin Schulz" <quentin.schulz@cherry.de>,
"Dmitry Baryshkov" <dmitry.baryshkov@oss.qualcomm.com>,
"Jose Quaresma" <jose.quaresma@oss.qualcomm.com>,
"Zoltán Böszörményi" <zboszor@gmail.com>
Subject: [PATCH v4 2/3] mesa-libclc: New recipe for forking libclc for Rusticl purposes in Mesa
Date: Fri, 7 Aug 2026 07:44:47 +0200 [thread overview]
Message-ID: <20260807054448.1301957-2-zboszor@gmail.com> (raw)
In-Reply-To: <20260807054448.1301957-1-zboszor@gmail.com>
See the reasoning and discussion at
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/43020
which was merged and backported to 26.2.0.
TL;DR: LLVM constantly introduces breaking changes that cause
regressions for running OpenCL CTS with Rusticl and finally
Karol Herbst had enough.
This fork is from the LLVM 22 version of libclc and contains the
necessary fixes to make Rusticl pass OpenCL CTS.
Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
---
meta/conf/distro/include/maintainers.inc | 1 +
.../mesa/mesa-libclc_22.1.8.3.bb | 26 +++++++++++++++++++
2 files changed, 27 insertions(+)
create mode 100644 meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb
diff --git a/meta/conf/distro/include/maintainers.inc b/meta/conf/distro/include/maintainers.inc
index c5b701c244..feccf29ce4 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -524,6 +524,7 @@ RECIPE_MAINTAINER:pn-menu-cache = "Ross Burton <ross.burton@arm.com>"
RECIPE_MAINTAINER:pn-mesa = "Unassigned <unassigned@yoctoproject.org>"
RECIPE_MAINTAINER:pn-mesa-demos = "Unassigned <unassigned@yoctoproject.org>"
RECIPE_MAINTAINER:pn-mesa-gl = "Unassigned <unassigned@yoctoproject.org>"
+RECIPE_MAINTAINER:pn-mesa-libclc = "Zoltán Böszörményi <zboszor@gmail.com>"
RECIPE_MAINTAINER:pn-mesa-tools-native = "Unassigned <unassigned@yoctoproject.org>"
RECIPE_MAINTAINER:pn-meson = "Trevor Gamblin <tgamblin@baylibre.com>"
RECIPE_MAINTAINER:pn-meta-environment-${MACHINE} = "Richard Purdie <richard.purdie@linuxfoundation.org>"
diff --git a/meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb b/meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb
new file mode 100644
index 0000000000..c93b5b9d9d
--- /dev/null
+++ b/meta/recipes-graphics/mesa/mesa-libclc_22.1.8.3.bb
@@ -0,0 +1,26 @@
+SUMMARY = "Mesa fork of libclc: Implementation of the library requirements of the OpenCL C programming language."
+HOMEPAGE = "https://gitlab.freedesktop.org/karolherbst/mesa-libclc/"
+SECTION = "devel"
+LICENSE = "Apache-2.0-with-LLVM-exception"
+LIC_FILES_CHKSUM = "file://LICENSE.TXT;md5=7cc795f6cbb2d801d84336b83c8017db"
+
+SRC_URI = "git://gitlab.freedesktop.org/karolherbst/mesa-libclc.git;protocol=https;branch=llvm_22"
+
+SRCREV = "87f66007242ff10e9e84bf32be84f9057f6abc75"
+
+inherit cmake pkgconfig
+
+# Depend explicitly on clang-native instead of using TOOLCHAIN as the build
+# objects from this recipe are build explicitly using clang for GPU targets.
+# We could INHIBIT_DEFAULT_DEPS to avoid any other toolchain but then we need
+# to wrestle CMake to configure without a toolchain.
+DEPENDS += "clang-native spirv-llvm-translator-native"
+
+# Semicolon-separated list of targets to build
+LIBCLC_TARGETS ?= "all"
+
+EXTRA_OECMAKE += "-DLIBCLC_TARGETS_TO_BUILD='${LIBCLC_TARGETS}'"
+
+FILES:${PN} += "${datadir}/mesa-clc"
+
+BBCLASSEXTEND = "native nativesdk"
--
2.55.0
next prev parent reply other threads:[~2026-08-07 5:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 5:44 [PATCH v4 1/3] mesa: Upgrade to 26.2.0 Zoltán Böszörményi
2026-08-07 5:44 ` Zoltán Böszörményi [this message]
2026-08-07 5:44 ` [PATCH v4 3/3] mesa, mesa-tools-native: Use mesa-libclc Zoltán Böszörményi
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=20260807054448.1301957-2-zboszor@gmail.com \
--to=zboszor@gmail.com \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=jose.quaresma@oss.qualcomm.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=quentin.schulz@cherry.de \
/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;
as well as URLs for NNTP newsgroup(s).