Jason Power 494f6a858e Ruby: Correct DataBlock =operator ... The =operator for the DataBlock class was incorrectly interpreting the class member m_alloc. This variable stands for whether the assigned memory for the data block needs to be freed or not by the class itself. It seems that the =operator interpreted the variable as whether the memory is assigned to the data block. This wrong interpretation was causing values not to propagate to RubySystem::m_mem_vec_ptr. This caused major issues with restoring from checkpoints when using a protocol which verified that the cache data was consistent with the backing store (i.e. MOESI-hammer).		2012-08-28 17:57:51 -05:00
..
arch	Clock: Add a Cycles wrapper class and use where applicable	2012-08-28 14:30:33 -04:00
base	Clock: Add a Cycles wrapper class and use where applicable	2012-08-28 14:30:33 -04:00
cpu	Clock: Add a Cycles wrapper class and use where applicable	2012-08-28 14:30:33 -04:00
dev	Clock: Add a Cycles wrapper class and use where applicable	2012-08-28 14:30:33 -04:00
doxygen	Fix up doxygen.	2006-08-14 19:25:07 -04:00
kern	syscall emulation: Enabled getrlimit and getrusage for x86.	2012-08-06 19:52:56 -07:00
mem	Ruby: Correct DataBlock =operator	2012-08-28 17:57:51 -05:00
python	Clock: Add a Cycles wrapper class and use where applicable	2012-08-28 14:30:33 -04:00
sim	Clock: Add a Cycles wrapper class and use where applicable	2012-08-28 14:30:33 -04:00
unittest	stats: Add stats unittest for total calculations.	2012-06-05 01:23:10 -04:00
Doxyfile	Fix up doxygen.	2006-08-14 19:25:07 -04:00
SConscript	swig: Disable unused value warning with llvm 3.1 compilers	2012-08-28 14:30:22 -04:00