Sergey Sharybin 5be97aba95 Recent spinlock commit made scheduling unsafe for threading ...

Namely, it caused nodes be adding to the pool multiple times.

Returned spin back, but use it only in cases node valency is
zero. So now valency is decreasing without any locks, then
if it's zero spin lock happens, node color (which indicates
whether node is scheduled or not) happens. Actual new task
creation happens outside of locks.

This might sound a bit complicated, but it's straightforward
code which is free from any thread synchronization latency.

2013-08-14 09:24:15 +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

cmake: remove set_lib_path macro

2013-06-17 18:15:56 +00:00

creator.c

Recent spinlock commit made scheduling unsafe for threading

2013-08-14 09:24:15 +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