Also, counting of faulting instructions (do we double-count) can also
get funny so you may want to double check that.
What you can do is place an assert that compares the two differing
numbers so that you find the exact spot where the inst counts start to
diverge.
On Fri, Aug 24, 2012 at 9:47 AM
I know nops don't get counted and I'm taking that into account. The -I
option exits based on thread[tid]->numInst, this is incremented in the same
way as committedInst, i.e., neither count nops. I can't see why if I exit
on thread[tid]->numInst == 1000, the stats file shows something different.
Th
typo:
*around line 1009
On Fri, Aug 24, 2012 at 9:20 AM, Korey Sewell wrote:
> I'm saying that the nops may not get counted in committedInsts. Other
> users have reported issues when comparing the committed instruction
> count between CPU models and typically this is the problem.
>
> If you look
I'm saying that the nops may not get counted in committedInsts. Other
users have reported issues when comparing the committed instruction
count between CPU models and typically this is the problem.
If you look in commit_impl.hh, around line 109, you'll see that
instDone() will not get called if th
This is the part of the code where the committedInsts get's incremented, so
it should match up with that and has nothing to do with the ops.
-Tony
On Fri, Aug 24, 2012 at 10:16 AM, Korey Sewell wrote:
> Tony,
> check the nop count. That might be the difference that you are seeing.
>
> -Korey
>
Tony,
check the nop count. That might be the difference that you are seeing.
-Korey
On Thu, Aug 23, 2012 at 1:24 PM, Anthony Gutierrez wrote:
> Hello,
>
> It seems that the number of committed instructions don't always match up
> with an instruction-based exit event, e.g., when using -I. The CPU
