It is m5-stable. Maybe I should change to m5. I can do that.
Also, are any of the binaries dependent on 1g2p-md.bin or 1g2p-hv.bin by any chance? Polina On Thu, Mar 5, 2009 at 1:24 PM, Steve Reinhardt <ste...@gmail.com> wrote: > m5 or m5-stable? The contextId change is in the former but not the latter. > > 2009/3/5 Polina Dudnik <pdud...@gmail.com>: > > I am doing it in m5. > > > > Polina > > > > - Show quoted text - > > On Thu, Mar 5, 2009 at 1:04 PM, Steve Reinhardt <ste...@gmail.com> > wrote: > >> > >> - Show quoted text - > >> 2009/3/5 Polina Dudnik <pdud...@gmail.com>: > >> > I am not sure why our code base would be different and by how much, > but > >> > that > >> > could be why yours is running fine and mine segfaults. > >> > >> Hi Polina, > >> > >> If you're doing this in the gem5 repository then that is getting stale > >> wrt the main m5 tree. It might be best if all you're doing is working > >> on SPARC functionality to do that based on the m5 tree. I really want > >> to have a do-over on the gem5 tree and make it such that Ruby vs. the > >> classic M5 memory system is a compile-time option so that we don't > >> have to have a permanent fork like we do now. > >> > >> Steve > >> _______________________________________________ > >> m5-dev mailing list > >> m5-dev@m5sim.org > >> http://m5sim.org/mailman/listinfo/m5-dev > > > > > > _______________________________________________ > > m5-dev mailing list > > m5-dev@m5sim.org > > http://m5sim.org/mailman/listinfo/m5-dev > > > > > _______________________________________________ > m5-dev mailing list > m5-dev@m5sim.org > http://m5sim.org/mailman/listinfo/m5-dev >
_______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev