I think it might be better to detect when you're going to stay in the
macroop before you get to the handler. If you need the microop to decide
to fetch and/or throw away the current macroop or not, and you need to
fetch (potentially) to create the macroop to create the microop, you end
up with
The regressions have been having some issues in the last couple of
days because the batch job scheduler died for some reason. I restarted
it and cleared out all the jobs.
Ali
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listin
That's an interesting optimization... sounds like maybe you don't want to
discard the macroop on a fault until you get into the fault handling
microcode and determine that it's a real fault and not one of these special
cases.
Steve
On Tue, Sep 23, 2008 at 11:07 PM, Gabe Black <[EMAIL PROTECTED]>
> oh i think I see now...
>
> This shadow set code and DSP/MT was done by myself and some of the MIPS
> guys...
>
> Anyway, the issue is probably that the value for "NumShadowSets" or
> something is set to 0 or a wrong value causing the bad access.
Well, if you look at the code in isa_traits.hh, Nu
oh i think I see now...
This shadow set code and DSP/MT was done by myself and some of the MIPS
guys...
Anyway, the issue is probably that the value for "NumShadowSets" or
something is set to 0 or a wrong value causing the bad access.
I'll see if I can look into it...
But this is an actual comp
> How's it a compiler error to do a unsigned integer comparison?
That's not the error. The error is that in the else clause, it's
guaranteed that the array access will be beyond the end of the array.
That's the error.
> In the MIPS ISA, I believe a bunch of registers were added into int reg.
> fi
How's it a compiler error to do a unsigned integer comparison?
In the MIPS ISA, I believe a bunch of registers were added into int reg.
file to maintain add in the MIPS MT /DSP compatibility.
However, this looks to be some shadow set register compatibility code that
got added...
On Wed, Sep 24, 2
I'm trying to get rid of lots of compiler warnings so that things work
properly with gcc 4.3 and I encountered something that's a bug.
In src/arch/mips/int_regfile.cc
The functions readReg and setReg both check to make sure that "intReg
< NumIntRegs" and do something special if it is. The confus
