Hi,

I get a lot of error messages while building gem5 which are related to 
uninitialized warnings being treated as errors. I tried adding specific flags 
for compiler to ignore this fact, but couldn't get past this check. Is there a 
single point in SConstruct(s), where I can force this behavior. Or, the 
generated file should have correct code.

For example, /python/swig/core_wrap.cc always fails to initialize PyObject 
*argv[2];

Thanks,
Uday

_______________________________________________
gem5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users

Reply via email to