Bug#1022577: llvm-toolchain-15 fails with LLVM ERROR when using mesa

Adrian Bunk bunk at debian.org
Mon Nov 21 11:35:07 GMT 2022


On Sun, Nov 13, 2022 at 12:04:07AM +0200, Adrian Bunk wrote:
> Control: close 1022576 22.2.3-1
> 
> On Sat, Nov 05, 2022 at 10:22:18AM +0000, Simon McVittie wrote:
> > Control: retitle -1 llvm-toolchain-15: Mesa on armel,armhf fails with LLVM ERROR: Cannot select
> > Control: tags -1 + patch fixed-upstream
> > 
> > On Mon, 24 Oct 2022 at 12:45:01 +0300, Adrian Bunk wrote:
> > > https://buildd.debian.org/status/fetch.php?pkg=mutter&arch=armhf&ver=43.0-3&stamp=1666029584&raw=0
> > > 
> > > ...
> > > # Start of pipeline tests
> > > LLVM ERROR: Cannot select: 0x1300f80: v4i32 = ARMISD::VCMPZ 0x1301c70, Constant:i32<2>
> > >   0x1301c70: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0xdf9afc, 0x131c538:1, Constant:i32<4>
> > >     0x131c538: i32,i32,ch = load<(load (s32) from %ir.209, align 8), <post-inc>> 0xdf9afc, 0x12fb7e0, Constant:i32<64>
> > >       0x12fb7e0: i32,ch = CopyFromReg 0xdf9afc, Register:i32 %23
> > >         0x12e99c0: i32 = Register %23
> > >       0x131a9a8: i32 = Constant<64>
> > >     0x1319fd0: i32 = Constant<4>
> > >   0x131a2e8: i32 = Constant<2>
> > > In function: fs_variant_partial
> > > ...
> > > 
> > > 
> > > Some discussion is in
> > > https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1993800
> > 
> > According to upstream bug <https://github.com/llvm/llvm-project/issues/58514>
> > this is fixed by commit
> > <https://github.com/llvm/llvm-project/commit/f970b007e55d6dab6d84d98a39658a58019eb06e>.
> 
> The reason why mesa hit this issue often has been fixed in mesa in [1],
> and I am closing the bug in mesa.
> 
> With current mesa all visible issues are gone,
> except perhaps mutter FTBFS.
> 
> mutter on armhf/armel went from 62 test failures to 1-2 test failures,
> I have not investigated whether they are due to this issue or unrelated.
>...

FYI:
mutter built on armhf/armel with the fixed LLVM.[1]

cu
Adrian

[1] I haven't double-checked that it was the LLVM patches and not 
    something unrelated that fixed the build.



More information about the Pkg-llvm-team mailing list