Re: [m5-dev] ISA specific decoder state

2008-09-24 Thread Gabe Black
Steve Reinhardt wrote: On Tue, Sep 23, 2008 at 9:37 PM, Ali Saidi [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: On Sep 23, 2008, at 9:28 PM, Steve Reinhardt wrote: I believe it's impossible fault on a microop in the middle of a macroop and then resume where you left off

Re: [m5-dev] Confusing MIPS code

2008-09-24 Thread Korey Sewell
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,

Re: [m5-dev] Confusing MIPS code

2008-09-24 Thread nathan binkert
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. file

Re: [m5-dev] Confusing MIPS code

2008-09-24 Thread Korey Sewell
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

Re: [m5-dev] Confusing MIPS code

2008-09-24 Thread nathan binkert
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,