On Mon, 23 Jul 2012, Kelly, Suzanne M wrote:
Greetings, Based on a web page review, we (the Sandia SST team) suspect
you had/are experiencing a similar problem when trying to build GEM5 on
some Red Hat systems. For us, the problem manifests itself when
compiling decoder.cc. The compilation consumes large amounts of CPU time
and never finishes because gcc requires over 15 GB of memory for the
compilation. decoder.cc is a generated file and is about 119,000 lines.
Our bailing wire is to recognize that the compile options being selected
are -g and -O3. With these options, the resulting object file (on a
system with sufficient memory) is 3.8 _GB_, With just -O3 the object
file is 12 MB. With just -g the object file is 16 MB. Based on some
testing, the problem is not unique to a specific version of gcc.
We are now running a local patch to remove the -g option. Unfortunately,
the change is applied to all objects generated as part of the gem5
build. Have you found a better solution? If you have any suggestions, we
would be happy to try them out.
Regards,
Sue Kelly
PS Our local GEM5 copy is changeset: 8642:549b72de8f72
Sue, you might want to take a look at how -Werror option can be set
specifically for a c/c++ file. Grep for Werror in the file src/SConscript.
It is plausible that something similar can be worked out for the -g
option.
--
Nilay
_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
