Ubuntu
mesa package

  1. Bug #1995137
  2. Comment #3

Comment 3 for bug 1995137

Revision history for this message
Isaac True (itrue) wrote (last edit ): Re: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64

Using this library results in the following error:

'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
WARNING: This target JIT is not designed for the host you are running. If bad things happen, please choose a different -march switch.
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
LLVM ERROR: Cannot select: 0x3fa81e7fa8: ch = store<(store 4 into %ir.mask_ptr1 + 12, basealign 16), trunc to i32> 0x3fa81eadd0, 0x3fa81eea00, 0x3fa81b3358, undef:i64
  0x3fa81eea00: i64 = sub Constant:i64<0>, 0x3fa81e7c68
    0x3fa81b59a8: i64 = Constant<0>
    0x3fa81e7c68: i64 = and 0x3fa81e7ed8, Constant:i64<1>
      0x3fa81e7ed8: i64 = srl 0x3fa81e9430, Constant:i64<7>
        0x3fa81e9430: i64,ch = load<(load 2 from %fixed-stack.5, align 8), zext from i16> 0x3fa80c34b8, FrameIndex:i64<-2>, undef:i64
          0x3fa81b2e78: i64 = FrameIndex<-2>
          0x3fa81b2da8: i64 = undef
        0x3fa81e7e70: i64 = Constant<7>
      0x3fa81b5a78: i64 = Constant<1>
  0x3fa81b3358: i64 = add FrameIndex:i64<6>, Constant:i64<28>
    0x3fa81b34f8: i64 = FrameIndex<6>
    0x3fa8217440: i64 = Constant<28>
  0x3fa81b2da8: i64 = undef
In function: fs_variant_partial
!!! Fatal signal received. Attempting cleanup, but deadlock may occur
pure virtual method called
terminate called without an active exception
!!! Fatal signal received. Attempting cleanup, but deadlock may occur
Mir fatal error: Unsupported attempt to continue after a fatal signal: SIGABRT

Matches this bug from Debian: https://<email address hidden>/msg139710.html