Hi Prannav,
Instcount was hard coded mostly as a sanity check to make sure the CPU wasn't
generating too many instructions. The number makes sense for reasonable
configurations of up to 4 CPUs, but at the time I wrote the code, I wasn't
expecting 16 core systems to be run. If you made changes to any of the O3 CPU
code I'd suggest you leave it in until you've fully tested it (just increase
the number); otherwise you can safely remove it or comment it out.
Kevin
Quoting prannav shrestha <[EMAIL PROTECTED]>:
> HIi all!!
> I amt trying to run 16 core O3CPU with 1 thread each core. I am getting error
> like:
>
> $ ../../build/ALPHA_SE/m5.opt -d out2 cmp16py --caches --detailed
> warn: Entering event queue @ 0. Starting simulation...
> m5.opt: build/ALPHA_SE/cpu/base_dyn_inst_impl.hh:132: void
> BaseDynInst<Impl>::initVars() [with Impl = O3CPUImpl]: Assertion `instcount
> <= 1510' failed.
> Program aborted at cycle 3642000
>
> in file base_dyn_inst_impl.hh , i found that
> ++instcount;
> if (instcount > 1500) {
>
> cpu->dumpInsts();
> #ifdef DEBUG
> dumpSNList();
> #endif
> assert(instcount <= 1500);
> }
> why is the instcount hardcoded to be less that 1500? highly appreciated, if
> someone could put some light on it.
>
> Thanks in advance
>
> prannav
>
>
>
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
