Sergey Sharybin 4bd4037276 Lock-free memory allocator ... Release builds will now use lock-free allocator by default without any internal locks happening. MemHead is also reduces to as minimum as it's possible. It still need to be size_t stored in a MemHead in order to make us keep track on memory we're requesting from the system, not memory which system is allocating. This is probably also faster than using a malloc's usable size function. Lock-free guarded allocator will say you whether all the blocks were freed, but wouldn't give you a list of unfreed blocks list. To have such a list use a --debug or --debug-memory command line arguments. Debug builds does have the same behavior as release builds. This is so tools like valgrind are not screwed up by guarded allocator as they're currently are. -- svn merge -r59941:59942 -r60072:60073 -r60093:60094 \ -r60095:60096 ^/branches/soc-2013-depsgraph_mt		2013-10-10 11:58:01 +00:00
..
cpp	code cleanup: some warnings and formatting for PyMethodDef's in the BGE.	2012-11-10 05:42:50 +00:00
intern	Lock-free memory allocator	2013-10-10 11:58:01 +00:00
test/simpletest	Added a brie instruction how to build simple memtest	2013-09-05 16:32:44 +00:00
CMakeLists.txt	Lock-free memory allocator	2013-10-10 11:58:01 +00:00
MEM_guardedalloc.h	Lock-free memory allocator	2013-10-10 11:58:01 +00:00
mmap_win.h	Mingw/Windows Compiling Fix	2013-09-01 05:12:36 +00:00
SConscript	Lock-free memory allocator	2013-10-10 11:58:01 +00:00