Re: [PATCH 15/33] target/ppc: Implement Vector Insert from GPR using GPR index insns

[BALATON Zoltan]

On Sat, 23 Oct 2021, Richard Henderson wrote:
> On 10/23/21 3:12 AM, BALATON Zoltan wrote:
> > You mentioning target_ulong reminded me a question I had. Currently we have 
> > qemu-system-ppc and qemu-system-ppc64 but the latter includes all machines 
> > of the former too so you could run for example sam460ex with 
> > qemu-system-ppc64 (except mac99 which behaves differently based on which 
> > executable it's part of but you could use mac99 -cpu G4 with 
> > qemu-system-ppc64 as well). But isn't target_ulong different in these 
> > executables and could that cause a problem with this? I've always used 
> > qemu-system-ppc for 32 bit machines but we could have one just executable 
> > for all machines if there's no need for both.
>
> Yes, we can, and probably should, have one executable for all PPC system 
> emulation.  RISCV is actively working toward that, and I think it would be 
> fairly easy for ARM and x86 to follow.
>
> It's something relatively easy to do that reduces the size of the test 
> matrix.

So may question was not if it's possible but if having target_ulong 
different from what we had in qemu-system-ppc could cause any problems? I 
have no experience running 32-bit guests with qemu-system-ppc64 but 
previously when this came up one difference pointed out was that 
target_ulong would change if I remember the discussion correctly, but 
nobody now if that could be a problem.

Regards,
BALATON Zoltan