Great work guys! It would probably be a good idea to also compile with RUBY=false every now and then to make sure no unintended dependencies crop up.
Gabe Quoting nathan binkert <[email protected]>: > Hi everyone, > > I just wanted to let both the GEMS people and the M5 people know that > after considerable work by a number of people, we've merged Ruby and > SLICC from GEMS into M5. This work is preliminary and is really only > for people that want to really get their hands dirty. Ruby is an > alternative to the current M5 memory system. To compile Ruby into M5, > you just get the latest source tree and compile with the RUBY=True > SCons command line option. The resulting binary will have all of the > old bits of M5 (including the existing memory system), but will also > add the RubyMemory object which can be used include a Ruby memory > system. There are lots of things todo, but we hope this is a good > initial step. > > For those of you that contribute to the M5 source tree, please compile > with RUBY=True if you are making changes that require that you run > regressions. This is especially important if you make changes to the > CPU models or the fundamental port/packet/request structures in the > memory system, but even if you don't, we'd like to have some coverage > on various systems. > > Over time, I suspect that we will change RUBY to default to True, then > eventually remove the RUBY parameter altogether. > > Thanks for all of the hard work that everyone did to make this happen! > > Nate > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
