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, 2008 at 9:35 AM, nathan binkert <[EMAIL PROTECTED]> wrote: > 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 confusion I have > comes from the fact that there is an else clause at all. The else > clause in the setReg case goes ahead and writes a value beyond the end > of the array if the condition is false. In both cases it falls back to the original register mapping. For setReg it writes the intReg index and for readReg it reads the intReg index. I'm not sure how the shadow-set stuff was implemented or stressed so I cant really say remove it with confidence. Looks like it would work tho... ---------- Korey L Sewell Graduate Student - PhD Candidate Computer Science & Engineering University of Michigan
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
