On 5 May 2014 13:09, Christopher Horler <cshor...@googlemail.com> wrote: > Public bug reported: > > I was reading the mailing list and saw NEON support in QEmu was making > progress. > > Is it not supported in user mode? or am I running into something else > here? (I've tried to include some what may be useful information)
Neon in the 32-bit CPUs has been supported for several releases now; what you're seeing is probably something else. > using qemu from git (last commits as below): > fdaad47 Merge remote-tracking branch > 'remotes/pmaydell/tags/pull-target-arm-20140501' into staging > e50bf23 Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into > staging > c090c10 Merge remote-tracking branch 'remotes/cohuck/tags/kvm_cap_helpers' > into staging > > (for completeness I should point out this is not actually > libQtCore.so.4.6.2 - the SONAME shows libQt5Core.so.5). > > chorler@linux-foxtrot:~/projects/src/CustomFirmware> qemu-arm -L ./root > ./root/usr/local/Trolltech/QtEmbedded-4.6.2-arm/lib/libQtCore.so.4.6.2 Are you trying to execute a DLL on purpose? > qemu: unhandled CPU exception 0x2 - aborting > R00=00000000 R01=f6c84fdd R02=00000000 R03=00000000 > R04=00000000 R05=00000000 R06=00000000 R07=00000000 > R08=00000000 R09=00000000 R10=f6ff9d80 R11=00000000 > R12=00000000 R13=f6c84d90 R14=00000000 R15=f6cdef74 > PSR=00000010 ---- A usr32 > qemu: uncaught target signal 6 (Aborted) - core dumped > Aborted This means your guest program tried to execute an SWI instruction which didn't have a sensible immediate value in it to be a Linux system call. This seems to me to be likely because we're trying to execute garbage because you've tried to execute a DLL rather than an executable. thanks -- PMM
