OK, great... it is pretty confusing to figure out which layer of the code
expects which type of register index. Getting the type system to enforce
this would be nice; how does that fit in with the other reorg stuff you
proposed a while ago?
In the meantime, I'll just commit my patch since it
I'm going to be pushing a lot of stuff soon, so please hold off on
pushing into the repository until that happens. I'm going to almost
empty my queue, but there's a hack in there to set up the Intel MP table
and maybe one or two other spots so that it has the right information
for more than one
It's mostly unrelated, but the two ideas would work together pretty well.
Gabe
Steve Reinhardt wrote:
OK, great... it is pretty confusing to figure out which layer of the
code expects which type of register index. Getting the type system to
enforce this would be nice; how does that fit in
* do-regression: qsub timed out, retrying locally
* build/ALPHA_SE/tests/fast/quick/01.hello-2T-smt/alpha/linux/o3-timing
passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-timing
Also, why do you change inst-readNextNPC() to inst-readNextPC()
in iew_impl.hh? Aren't you going to then print the same value twice?
Well, I'm trying to fix error'd DPRINT statements here.
In the DPRINT, it says NPC, but it's printing out the NNPC which was
confusing to me. So maybe the
All the regressions passed with my changes applied except for tsunami-o3
and tsunami-o3-dual. Those had run for 15 hours and not finished when I
checked on them which is obviously way to long. I removed my patches and
tried it on the head, but it's been running there for an hour and still
hasn't
Those tests passed on April 5 and took 395 and 440 seconds on zizzer,
respectively. So (1) they must have broken since then and (2) if they're
taking longer than 10 minutes or so (depending on where you're running them)
they're definitely broken.
Steve
On Thu, Apr 16, 2009 at 9:08 PM, Gabe
