Control: tags -1 + pending
On Wed, 04 Sep 2024 at 18:51:11 +0100, Simon McVittie wrote:
> src:gtk4 uses GALLIUM_DRIVER=softpipe on mips*, powerpc and sparc* to work
> around #1010838. Mesa 24.2.x is no longer built with softpipe enabled
24.2.1-4 re-enables softpipe (#1080475) which should resolve this for
mips*, powerpc and sparc*. The new Mesa version has not compiled on
buildds yet, but when it has, I'll check whether it fixes the build
regression on mips64el. Hopefully we can also start using softpipe on
riscv64 as a workaround for #1080435, until that gets fixed.
If there are -ports architectures where llvmpipe is known-broken,
I don't mind adding them to the list of architectures where we use
GALLIUM_DRIVER=softpipe - but I would suggest that as a longer-term
plan to have working GL everywhere, porters should look into fixing
llvmpipe for their architecture (via changes in Mesa and/or LLVM) if
necessary. The addition of an ORCJIT code path in Mesa seems like a
really big step towards this.
> I'm doing a gtk4 build on the mips64el porterbox eberlin to assess whether
> we can use the new ORCJIT llvmpipe and remove the workaround for #1010838
Unfortunately the answer seems to be "no we can't": lots of tests still
fail on mips64el with ORCJIT llvmpipe. I haven't looked into the failures
in detail, but this does not seem to be the same problem as on riscv64
(#1080435, #1080493) since the patch that has been suggested for the
riscv64 issue is in riscv64-specific code.
I haven't tried the -ports architectures with llvmpipe: they might be OK
with llvmpipe now, or they might still have similar problems. If a porter
wants to look into this, please look for "GALLIUM_DRIVER=softpipe"
in debian/rules and it should be obvious from there how to disable the
workaround. Testing the gtk4 4.15.x from experimental is more important
than the gtk4 4.14.x in testing/unstable right now, because we're hoping
to upload 4.15.x/4.16.x to unstable soon (it's required for GNOME 47).
smcv
