On Mon, Dec 23, 2013 at 10:17:15PM +0000, Peter Maydell wrote: > FWIW mainline's handling of this insn doesn't have this bug.
OT: Is there a clear explanation of the various aarch64 trees? I noticed that upstream qemu has some files like target-arm/ translate-a64.c, but it didn't (and still doesn't) appear to work: + ./configure '--target-list=arm64-linux-user i386-softmmu x86_64-softmmu arm-softmmu ppc-softmmu ppc64-softmmu' '--extra-ldflags=-pie -Wl,-z,relro -Wl,-z,now' '--extra-cflags=-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -fPIE -DPIE' --disable-werror --disable-xen --enable-kvm --enable-tpm ERROR: Unknown target name 'arm64-linux-user' I found the SuSE tree and it works, but the code is quite different from the upstream tree. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top
