From: Quentin Schulz <quentin.schulz@cherry.de>
To: "Zoltán Böszörményi" <zboszor@gmail.com>,
openembedded-core@lists.openembedded.org
Cc: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Jose Quaresma <jose.quaresma@oss.qualcomm.com>
Subject: Re: [PATCH v4 2/3] mesa-libclc: New recipe for forking libclc for Rusticl purposes in Mesa
Date: Fri, 21 Aug 2026 20:05:45 +0200 [thread overview]
Message-ID: <45dbe3e7-2ae2-44bd-b39f-014ab79fc001@cherry.de> (raw)
In-Reply-To: <20260807054448.1301957-2-zboszor@gmail.com>
Hi Zoltán,
On 8/7/26 7:44 AM, Zoltán Böszörményi wrote:
> 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/"
Sorry for the mangled link. Sad that they still keep this in Karol's
namespace. It however matches what they use in their CI (via the GitLab
Project ID), see .gitlab-ci/container/build-libclc.sh.
> +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"
How do we make sure we use the mesa-libclc blessed by mesa for a given
release?
It seems like we should use the tag as specified in
MESA_LIBCLC_VERSION=22.1.8.3 in .gitlab-ci/container/build-libclc.sh.
Can you add a comment in mesa-libclc and mesa.inc that mesa-libclc
should only be bumped with mesa.inc, and that a bump in mesa.inc should
REEEEEEALLLLLLY check we use the expected mesa-libclc version (put it
next to SRCREV so it appears in the git context when someone sends a patch).
I've only barely looked at the changes made between 26.1.0 and 26.2.0
but we should be able to drastically relax the libclc requirement for
anything but opencl (rusticl). c.f. 20b40644b7ae ("clc: make libclc
optional for configs not needing it")
Someone will need to start looking into what they're doing with
panfrost, c.f. the new panfrost-rust option. There's a bunch of
additional dependencies in src/panfrost/compiler/kraid/meson.build we'll
need. Oh well, something for later (but probably very soon, like next
release).
Cheers,
Quentin
next prev parent reply other threads:[~2026-08-24 7:58 UTC|newest]
Thread overview: 5+ 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 ` [PATCH v4 2/3] mesa-libclc: New recipe for forking libclc for Rusticl purposes in Mesa Zoltán Böszörményi
2026-08-10 17:17 ` [OE-core] " Ross Burton
2026-08-21 18:05 ` Quentin Schulz [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=45dbe3e7-2ae2-44bd-b39f-014ab79fc001@cherry.de \
--to=quentin.schulz@cherry.de \
--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=zboszor@gmail.com \
/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