On 9 June 2014 06:59, Chaos Shu wrote:
> I’ve noticed that Qemu maintained the target arch register in memory for
> capacity, but the load/store really cost a bit much, is there any way map
> the register directly.
Our JIT's register allocator will avoid storing the guest register value
back to R
Hi all
I've noticed that Qemu maintained the target arch register in memory for
capacity, but the load/store really cost a bit much, is there any way map
the register directly.
For example, in x86 to aarch64, x86 uses 8 registers mostly such eax ebx ecx
and so on, and aarch64 arch got 31 ge