*
build/ALPHA_SE_MOESI_hammer/tests/fast/quick/00.hello/alpha/tru64/simple-timing-ruby-MOESI_hammer
passed.
*
build/ALPHA_SE_MOESI_hammer/tests/fast/quick/60.rubytest/alpha/linux/rubytest-ruby-MOESI_hammer
passed.
*
I tried M5_DUMMY_RETURN and it it not working. I checked its definition.
It would evaluate to nothing, in which case I do not see why it should
help in avoiding the warning. I tried putting a return statement before
panic();
return panic(not implemented);
This works with GCC 4.2.2.
I
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/335/
---
Review request for Default.
Summary
---
This is a review request for the
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/359/
---
(Updated 2010-12-24 09:02:20.653744)
Review request for Default.
Changes
---
---
This is an automatically generated e-mail. To reply, visit:
http://reviews.m5sim.org/r/358/
---
(Updated 2010-12-24 09:04:02.816498)
Review request for Default.
Changes
---
Long story, but CountedDrainEvent is bugging me (again)... it's not an event
(it never gets scheduled; it's just a callback) and it derives unnecessarily
from SimLoopExitEvent (it just uses the inherited cause and code fields to
set the cause and code fields of a new SimLoopExitEvent it
I looked a little more at the base dir, and there are a bunch more files are
also unused (at least to the extent that I compiled everything successfully
after I removed them).
R src/base/compression/base.hh
R src/base/compression/lzss_compression.cc
R src/base/compression/lzss_compression.hh
I am in complete agreement with you. But I do not want to keep the
repository in a broken state.
Ok. I like that attitude.
Nate
___
m5-dev mailing list
m5-dev@m5sim.org
http://m5sim.org/mailman/listinfo/m5-dev
