On Tue, 28 Apr 2015, Beckmann, Brad wrote:
The tester has always been a single object (since 1999!). The tester works in a coordinated fashion to instigate races. It does not operate as separate independent objects.
Brad, even if it has been a single object for a long time, I still believe it is not the right way. If we have multiple objects, we should still be able to make them work in a coordinated fashion by letting them share some portion of memory. I did this by marking the CheckTable static, but I am willing to make it common to every tester object in a different fashion. Can you explain what may prevent us from coordinating multiple tester objects?
Again, I do not want to create separate code for testing and for simulation. There are several places in ruby where we do this and I think we should do away with them, instead of further spreading this approach.
-- Nilay _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
