From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <mangadi@qti.qualcomm.com>, <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] weston: backport gl-shaders fix to avoid shader compiler crashes
Date: Fri, 17 Apr 2026 10:12:35 +0200 [thread overview]
Message-ID: <DHVA1T5G5BSM.1PPMQ6SPQQC5X@bootlin.com> (raw)
In-Reply-To: <DHOHLMLD4MQ9.34VQG7IIO7F3C@bootlin.com>
On Thu Apr 9, 2026 at 10:38 AM CEST, Mathieu Dubois-Briand wrote:
> On Tue Apr 7, 2026 at 11:47 AM CEST, Mahesh Angadi via lists.openembedded.org wrote:
>> Some GPU shader compilers do not optimize away unused YUV shader
>> uniforms, even when the associated code paths are unreachable. This can cause
>> Weston to hit assertion failures at runtime on non-Mesa platforms, despite
>> working correctly on Mesa-based drivers.
>>
>> Backport the upstream gl-shaders fix to restore stable behavior across
>> GPU drivers.
>>
>> Signed-off-by: Mahesh Angadi <mangadi@qti.qualcomm.com>
>> ---
>
> Hi Mahesh,
>
> I note this is breaking builds with meta-qcom, as the patch is also
> present in there. But as you are the author of changes in both side, I
> bet you already knew this. :)
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/113/builds/565
>
> Thanks,
> Mathieu
Hi Mahesh,
This patch is now merged into master, so builds with meta-qcom are now
failing. Are you taking care of fixing this into meta-qcom or should I
contact maintainers?
https://autobuilder.yoctoproject.org/valkyrie/#/builders/113/builds/619
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-04-17 8:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 9:47 [PATCH] weston: backport gl-shaders fix to avoid shader compiler crashes Mahesh Angadi
2026-04-09 8:38 ` [OE-core] " Mathieu Dubois-Briand
2026-04-17 8:12 ` Mathieu Dubois-Briand [this message]
2026-04-17 13:07 ` Jose Quaresma
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=DHVA1T5G5BSM.1PPMQ6SPQQC5X@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=mangadi@qti.qualcomm.com \
--cc=openembedded-core@lists.openembedded.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