On 05/15/2015 01:52 PM, Peter Crosthwaite wrote: > 2: Core code is converted to not use "target_ulong" (tcg_core_ulong?) > and target_ulong becomes a target-specific code concept.
This is my favorite. I did poke around with new tcg opcodes to break some of the TARGET_LONG_BITS usage in the tcg backend. It wasn't terribly difficult until I reached the memory helpers. Aside from target_ulong addr, there's also TARGET_PAGE_MASK, TARGET_PAGE_SIZE, TARGET_PAGE_BITS, CPU_TLB_SIZE. What's our position on the compatibility of the mmu between the multi-arch platforms? I assume at the moment they must be all the same? Of course, I've mentioned before that ARM might well benefit from having these values be variable and not constant at all. Primarily because of the armv5 1K pages affecting aarch64. r~
