btw, on my corei5, in debug build, reduce (using double): 11msec non_parallel: 37msec parallel with atomicOp: 123msec
so, that is the reason for using parallel reduce, assuming the ulong range thing will get fixed.
Jay Norwood via Digitalmars-d-learn Sat, 26 Sep 2015 09:21:11 -0700
btw, on my corei5, in debug build, reduce (using double): 11msec non_parallel: 37msec parallel with atomicOp: 123msec
so, that is the reason for using parallel reduce, assuming the ulong range thing will get fixed.