2026. 07. 21. 11:01 keltezéssel, Quentin Schulz írta:
Hi Zoltán,
On 7/21/26 6:08 AM, Böszörményi Zoltán wrote:
2026. 07. 20. 16:43 keltezéssel, Quentin Schulz írta:
Hi Zoltan, everybody,
On 7/19/26 10:01 AM, Zoltan Boszormenyi via lists.openembedded.org wrote:
See the reasoning and discussion at
https://eur02.safelinks.protection.outlook.com/?
url=https%3A%2F%2Fgitlab.freedesktop.org%2Fmesa%2Fmesa%2F-
%2Fmerge_requests%2F43020&data=05%7C02%7Cquentin.schulz%40cherry.de%7Cebbe0f4e8df54c2c252b08dee6ddba7e%7C5e0e1b5221b54e7b83bb514ec460677e%7C0%7C0%7C639202037154557993%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=JWuaPEkNjN6Y5zTeDBao%2Fk0bDR1FKZsaOgDck4evP2E%3D&reserved=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.
I think this may be too early as this is still pending upstream and is currently not
receiving support from at least one person involved there.
That one person's objection is now alleviated by not requiring
the mesa-libclc dependency exclusively. It was replaced by
a runtime check and a warning when not running this fork.
As a result, the mesa-libclc repo was rebased twice since I posted this recipe.
Rebasing is a big issue for us. I'm assuming Karol knows better and won't do it once
it's actually used by mesa officially.
So the MR is still definitely in flux.
Hopefully, by 26.2.0, it plays out and gets backported.
Not sure they will want to backport it but let's see.
Two out of the three commits have the "Backport-to: *" line.
So if this MR happens to get merged before 26.1 is EOL,
they will get into that version, too, in a slightly different form,
as the first one changes the context for the two later commits.
I'm assuming they will not do releases on that fork, are we expected to always update
whenever there's a new commit? How do we make sure we use a version of libclc they are
expecting us to use with mesa? (e.g. not forget to bump mesa-libclc when we update mesa).
I will keep an open eye on the mesa-libclc project.
Eventually I would like to see Rusticl replace intel-compute-runtime,
of which the legacy version (requiring LLVM 14!) is carried forward
in my meta-clang-revival layer, forked from an older meta-intel branch.
Also, aren't we going to have an issue if we have libclc AND mesa- libclc built at the
same time?
No, because they install differently names files or into different locations.
For mesa-libclc, the pkgconfig file is renamed and the install path
is ${datadir}/mesa-clc.
ACK.
Cheers,
Quentin
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#241583):
https://lists.openembedded.org/g/openembedded-core/message/241583
Mute This Topic: https://lists.openembedded.org/mt/120341489/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
