asavah <irher...@gmail.com> writes:
> Public bug reported: > > 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 I should point out that a rpi3 is a cortex-a53 so -cpu cortex-a53 should be all you need to run the binaries. -cpu max will enabled a bunch of features you cannot use on an actual pi. > > --- 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. > > ** Affects: qemu > Importance: Undecided > Status: New -- Alex Bennée