On 03/06/2015 08:04 AM, Alexander Graf wrote:
> Hi Richard,
>
> 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 S
On Fri, 6 Mar 2015, Alexander Graf wrote:
> >> 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, becau
> Am 06.03.2015 um 18:20 schrieb Maciej W. Rozycki :
>
>> 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
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 instr
