> It might appear as if coherence protocols are the only thing that is there > to ruby. If some time down the line, protocols were to become optional > meaning you could use some part of ruby with out using the coherence > protocols themselves, would you still want to go on with the check on the > variable PROTOCOL? The variable PROTOCOL should only be used for things > related to protocols themselves. Why would you want to use it to enable / > disable options for, say, topology? In the long run, we want to get rid of as many compile time options as possible. If there are useful parts of ruby that are not part of a protocol, then we should always just compile them in.
Nate _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
