> Am 06.03.2015 um 18:20 schrieb Maciej W. Rozycki <ma...@linux-mips.org>:
>
>> On Fri, 6 Mar 2015, Alexander Graf wrote:
>>
>> I've finally managed to check out why my e500v2 automated tests fail to
>> run. Apparently they break because autotest wants to execute target code
>> and runs into an illegal instruction while doing that:
>>
>> Program received signal SIGILL, Illegal instruction.
>> 0xb57c84cc in ?? ()
>> (gdb) x /i $pc
>> => 0xb57c84cc: mfocrf r0,1
>>
>> And lo and behold, I really couldn't find any reference to mfocrf in the
>> e500v2 spec.
>
> Do real e500 processors trap on this operation as well?
The illegal instruction I posted about above was when running qemu *on* e500v2,
because TCG emits mfocrf ;).
Alex
