On Fri, Jun 08, 2012 at 02:04:40AM +0100, Maciej W. Rozycki wrote:
>
> This change updates the CPU reset sequence to use a common piece of code
> that figures out CPU state flags, fixing the problem with MIPS_HFLAG_COP1X
> not being set where applicable that causes floating-point MADD family
>
On Fri, 8 Jun 2012, Andreas Färber wrote:
> >>> The problem was seen with the 24Kf MIPS32r2 processor in user emulation.
> >>>
> >>> The new approach prevents system and user emulation from diverging -- all
> >>> the hflags state is initialized in one place now.
> >>
> >> I submitted a patch
Am 08.06.2012 18:20, schrieb Maciej W. Rozycki:
> On Fri, 8 Jun 2012, Meador Inge wrote:
>
>>> The problem was seen with the 24Kf MIPS32r2 processor in user emulation.
>>> The new approach prevents system and user emulation from diverging -- all
>>> the hflags state is initialized in one place
On Fri, 8 Jun 2012, Meador Inge wrote:
> > The problem was seen with the 24Kf MIPS32r2 processor in user emulation.
> > The new approach prevents system and user emulation from diverging -- all
> > the hflags state is initialized in one place now.
>
> I submitted a patch to fix this issue and
On 06/07/2012 08:04 PM, Maciej W. Rozycki wrote:
> This change updates the CPU reset sequence to use a common piece of code
> that figures out CPU state flags, fixing the problem with MIPS_HFLAG_COP1X
> not being set where applicable that causes floating-point MADD family
> instructions (and o
