Am 06.05.2012 22:01, schrieb malc:
> On Sun, 6 May 2012, Andreas F?rber wrote:
>
>> For targets where TARGET_LONG_BITS != 32, i.e. 64-bit guests,
>> addr_reg is moved to r4. For hosts [without] TCG_TARGET_CALL_ALIGN_ARGS
>> either data_reg2 or data_reg or a masked version thereof would overwrite
>
Am 06.05.2012 21:38, schrieb Andreas Färber:
> For targets where TARGET_LONG_BITS != 32, i.e. 64-bit guests,
> addr_reg is moved to r4. For hosts with TCG_TARGET_CALL_ALIGN_ARGS
Er, obviously I meant "without". :)
/-F
> either data_reg2 or data_reg or a masked version thereof would overwrite
> r
On Sun, 6 May 2012, Andreas F?rber wrote:
> For targets where TARGET_LONG_BITS != 32, i.e. 64-bit guests,
> addr_reg is moved to r4. For hosts with TCG_TARGET_CALL_ALIGN_ARGS
> either data_reg2 or data_reg or a masked version thereof would overwrite
> r4. Place it in r5 instead, matching TCG_TARGE
For targets where TARGET_LONG_BITS != 32, i.e. 64-bit guests,
addr_reg is moved to r4. For hosts with TCG_TARGET_CALL_ALIGN_ARGS
either data_reg2 or data_reg or a masked version thereof would overwrite
r4. Place it in r5 instead, matching TCG_TARGET_CALL_ALIGN_ARGS hosts.
This might explain crashe
