I've run into similar problems on MacOS, but they seem to very compiler dependent. Turning off optimization helps as well.
From: Steve Reinhardt <ste...@gmail.com<mailto:ste...@gmail.com>> Reply-To: gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> Date: Monday, January 7, 2013 10:30 AM To: gem5 users mailing list <gem5-users@gem5.org<mailto:gem5-users@gem5.org>> Subject: [EXTERNAL] Re: [gem5-users] Gem5 compiling error 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
_______________________________________________ gem5-users mailing list gem5-users@gem5.org http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
