As requested I tarred the failing binaries. The first one (first case in the original report) is g-ir-compiler from gobjact-introspection, this one has another interesting detail: if compiled with -mcpu=cortex-a53 -mfpu=neon-fp-armv8 (the correct flags for raspberry pi 3) it crashes on 4.0.0-rc, but works fine even on 4.0.0 if compiled with -mcpu=cortex-a53 -mfpu=neon-vfpv4 , on 3.1.0 it runs fine with -mfpu=neon-fp-armv8 .
The second one (second case in original report), I'm not sure if its the llvm-config binary itself, or the code from libLLVM so I attached the whole thing. It only crashes if called with llvm-config --shared-mode , llvm-config --version and llvm-config --ldflags works fine. -mfpu=neon-vfpv4 does not help here, crashes anyway, but has worked fine with 3.1.0 ** Attachment added: "bug1821430.tar.xz" https://bugs.launchpad.net/qemu/+bug/1821430/+attachment/5248857/+files/bug1821430.tar.xz -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1821430 Title: qemu-user-arm (4.0.0-rc0) crashes Status in QEMU: New Bug description: I'm using qemu-user-arm for crosscompilation needs, usually via a wrapper. qemu-user-arm (4.0.0-rc0) crashes with SIGILL on at least 2 instructions: first case (sadly I don't have more data handy, can reproduce at a later time if needed): (gdb) x/i $pc => 0xfffce314: vseleq.f64 d0, d17, d0 second case (llvm-config): qemu cmdline: qemu-arm -strace -cpu max -r 5.0.0 -L /home/asavah/kross/build/rpi3/rootfs -E LD_LIBRARY_PATH=/home/asavah/kross/build/rpi3/rootfs/usr/bin:/home/asavah/kross/build/rpi3/rootfs/usr/lib /home/asavah/kross/build/rpi3/rootfs/usr/bin/llvm-config --shared-mode --- SIGILL {si_signo=SIGILL, si_code=2, si_addr=0xf9f89f80} --- qemu: uncaught target signal 4 (Illegal instruction) - core dumped output from gdb(arm) attached to qemu-user-arm Program received signal SIGILL, Illegal instruction. 0xf9f77f80 in ?? () (gdb) bt #0 0xf9f77f80 in ?? () #1 0xfffd796c in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) (gdb) x/i $pc => 0xf9f77f80: vrintm.f64 d18, d18 The very same binaries when run with qemu-user-arm 3.1.0 (both from ubuntu 19.04 package and self built) work flawlessly. This is clearly a regression. Please fix before releasing 4.0.0. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1821430/+subscriptions