Good point... I was probably compiling gem5.debug not gem5.opt. Perhaps we should implement some of the features we came up with long ago to split the decoder.cc output into multiple files.
Steve On Mon, Jan 7, 2013 at 9:52 AM, Nilay Vaish <ni...@cs.wisc.edu> wrote: > On Mon, 7 Jan 2013, Steve Reinhardt wrote: > > I'm even further behind than Andreas, but I'm curious about the situation >> here. It's been a while, but last time I checked, compiling the x86 >> decoder with gcc took about 1GB of RAM (definitely <1.5GB). If something >> has happened to the code and/or gcc that really makes it take much more >> than that, I'm very interested in knowing. >> >> In my experience, running in limited-memory situations because I'm >> compiling in a VM on my laptop, something like 2-3GB of physical memory is >> plenty if you're running scons with "-j 2" (or not using -j at all). If >> you're running into problems with 4GB of RAM, make sure you're not using a >> -j argument larger than 2, and that you don't have any other large >> memory-consuming processes running. >> >> > Steve, are you talking about gem5.opt? > > -- > Nilay >
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
