* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/linux/o3-timing passed.
* build/ALPHA_SE/tests/fast/quick/00.hello/alpha/tru64/simple-timing passed.
* build/ALPHA_SE/tests/fast/quick/20.eio-short/alpha/eio/simple-atomic
passed.
*
changeset c36087d4573d in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=c36087d4573d
description:
Reference updates. Since split cache is gone, a lot of config.ini
changes, and minor changes to stats that are likely due to the decoupling of
insertions/evictions in the
changeset f693fcdd4aa5 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=f693fcdd4aa5
description:
Automated merge with ssh://daystrom.m5sim.org//repo/m5
diffstat:
140 files changed, 65 insertions(+), 526 deletions(-)
So, Packet and Request have lots of functions called getFoo and
setFoo. That sort of style has always annoyed me because it requires
a lot of extra typing and space. e.g.
/// Accessor function for the destination index of the packet.
short getDest() const { assert(destValid); return
What's the convention in other objects? I'm fine with either approach
(though I lean toward what Nate is suggesting); as with most style
things, I'm more concerned with consistency than anything else. I'd
be OK with this if it's part of a trend toward doing accessors in this
style globally (in
I'm fine with it shifting to this method Too bad that C++ doesn't
have Objective-C like properties.
Ali
On Nov 6, 2008, at 2:10 PM, Steve Reinhardt wrote:
What's the convention in other objects? I'm fine with either approach
(though I lean toward what Nate is suggesting); as with most
I prefer Nate's way too - members be _member, and accessor be member().
I half did this with my contextId()/cpuId()/threadId() changes just now. my
set functions were still prepended with set though, didn't think of
overloading.
Anyway, point is, I'm down.
Lisa
On Thu, Nov 6, 2008 at 2:16 PM,
This is a bug, though it causes neither crashes nor functional
misbehavior. The bug is that a class deriving from both RefCounted and
FastAlloc steals memory away from the FastAlloc system. The delete
operator called by RefCounted is NOT the overloaded one that FastAlloc
uses, so the block
This is a bug, though it causes neither crashes nor functional
misbehavior. The bug is that a class deriving from both RefCounted and
FastAlloc steals memory away from the FastAlloc system. The delete
operator called by RefCounted is NOT the overloaded one that FastAlloc
uses, so the block of
changeset 61c838ecc225 in /z/repo/m5
details: http://repo.m5sim.org/m5?cmd=changeset;node=61c838ecc225
description:
tracediff: add '#' support for sub-arg alternatives, '-n' param
diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
util/tracediff |2 +-
diffs (105 lines):
diff
10 matches
Mail list logo
