There seem to be a few issues with the comInstEventQueue. Although the queue 
counts instructions, it is still subject to the assert(when >= curTick); 
assertion. Additionally, there doesn't seem to be any way to find out what the 
current instruction is to make sure that the scheduling always happens in the 
future. 

Nate, the only thing I can think to do is have a parameter for if the assert 
should be checked (either a variable or a template parameter), thoughts?

Anyone mind if I get rid of the instCount() function/variable that was used for 
legion validation and create a virtual function in BaseCpu that returns numInst?

Thanks,
Ali

_______________________________________________
m5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/m5-dev

Reply via email to