On 16 June 2013 21:06, Andreas Färber wrote:
> My qom-cpu-10 series may help here, it turns cpu_dump_state() into a
> simple helper function calling CPUClass::dump_state(). So a Cortex-A5x
> class_init or TARGET_AARCH64 for the base class_init would simply assign
> the 64-bit version of the callba
Am 20.05.2013 14:57, schrieb Peter Maydell:
> On 14 May 2013 05:32, John Rigby wrote:
>> @@ -10038,6 +10042,11 @@ void cpu_dump_state(CPUARMState *env, FILE *f,
>> fprintf_function cpu_fprintf,
>> int i;
>> uint32_t psr;
>>
>> +if (is_a64(env)) {
>> +cpu_dump_state_a64(env,
On 14 May 2013 05:32, John Rigby wrote:
> @@ -10038,6 +10042,11 @@ void cpu_dump_state(CPUARMState *env, FILE *f,
> fprintf_function cpu_fprintf,
> int i;
> uint32_t psr;
>
> +if (is_a64(env)) {
> +cpu_dump_state_a64(env, f, cpu_fprintf, flags);
> +return;
> +}
>
From: Alexander Graf
We should translate AArch64 mode separately from AArch32 mode. In AArch64 mode,
registers look vastly different, instruction encoding is completely different,
basically the system turns into a different machine.
So let's do a simple if() in translate.c to decide whether we c
