On Thu, 2 Jul 2015, Jason Power wrote:
On July 2, 2015, 5:31 a.m., Nilay Vaish wrote:
Brandon, overall I would suggest, if it is possible, that you spend sometime on
making
RubySystem a sim object. That way you would not require to copy the pointer to
so
many places. I think objects that need clock really should be clocked objects
themselves or hold pointer to some real clocked object. RubySystem is really a
glue
object which should not have a clock of its own.
Maybe this is what you meant, but reimplementing RubySystem as a SimObject
should be a different patch. This patch takes a step in the right direction.
No. I wrote what I meant.
--
Nilay
_______________________________________________
gem5-dev mailing list
gem5-dev@gem5.org
http://m5sim.org/mailman/listinfo/gem5-dev
