> I've never used AverageDeviation. If I recall, I read about it on the twiki
> and it's kind of random, could be useful but not really a standard stat, so
> if it's super broken then I think it's ok to nuke it.
> I like the Distribution stats, I've been using them a fair amount in my
> tree, which
Hi Nate,
I've never used AverageDeviation. If I recall, I read about it on the twiki
and it's kind of random, could be useful but not really a standard stat, so
if it's super broken then I think it's ok to nuke it.
I like the Distribution stats, I've been using them a fair amount in my
tree, whic
I'm thinking you should nuke it. What I do for things like that is
just make a patch with mq. That way you always have access to it, but
it doesn't otherwise clutter things up for you or anybody else.
Gabe
Quoting Korey Sewell :
Good points, Sorry about that. As the comment says, that's ju
Good points, Sorry about that. As the comment says, that's just a stat that
I was using a while back for debugging but cluttered things up when I was
looking at the "real" processor stats.
maybe a "#if 0" will do or I can just get rid of them altogether.
I'm leaning toward the former though as t
changeset 333ca39e832a in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=333ca39e832a
description:
inorder: update regressions from RAS fix
diffstat:
tests/long/50.vortex/ref/alpha/tru64/inorder-timing/simout|6 +-
tests/long/50.vortex/ref/alpha/tru64/inorder-tim
changeset cd42a32dc8b6 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=cd42a32dc8b6
description:
inorder: Return Address Stack bug
the nextPC was getting sent to the branch predictor not the current PC,
so
the RAS was returning the wrong PC and mispredict
changeset b10c66a125f6 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=b10c66a125f6
description:
inorder: resource scheduling backend
replace priority queue with vector of lists(1 list per stage) and place
inside a class
so that we have more control of wh
Hi Korey,
You really threw me for a loop with this one... I was testing out a
simple change, which I often do using m5.debug since it compiles
faster, and the inorder tests kept failing. I could see that it was
due to some changes you made recently, but I had pulled both the code
changes and the
changeset 6a854784be4f in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=6a854784be4f
description:
X86: Fix div2 flag calculation.
diffstat:
src/arch/x86/isa/microops/regop.isa | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diffs (12 lines):
diff -r 1b1f8f32
