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
..
blender.map	Attempt to fix #35228: hide a few LLVM symbols that are not in the llvm namespace	2013-05-06 09:44:56 +00:00
buildinfo.c	style cleanup: mostly whitespace in rna	2012-05-12 11:01:29 +00:00
CMakeLists.txt	Photoshop PSD support	2013-10-08 21:17:24 +00:00
creator.c	Lock-free memory allocator	2013-10-10 11:58:01 +00:00
osx_locals.map	OSX/scons: introducing and testing an unexported_symbols_list to prevent clashes, todo: cmake	2012-11-27 11:38:59 +00:00