Andrew

1/ TBB equivalents of OMP PARALLEL pragmas 2/ TBB mutexes 3/ TBB malloc in place of current sbrk/mmap allocator

Open a new issue since it is not related to TBB. Documentation is in Makefile.rule - USE_THREAD=0 USE_LOCKING=1

All 3 your threads will be serialized in 3-thread 'thread'. If your 3 threads are processes it will work as you expect.

If you use_thread=0 but keep use_locking then you can schedule your single-threaded calls from your code. You cannot have both at once.

There is common structure in memory.c that tracks allocations and you need locking for that. USE_THREAD means dllinit()/.init() will start thread per core at startup, for aforementioned reason locking is...

OpenBLAS locks own critical structures when single-threaded version is called concurrently. Obviously you have to barrier writes to not have them concurrenlty in same place, and then barrier reads to...

Some seem just duplicate generic kernels?

you have iomp5 symbols in your build output. You need to start with a clean source tree and make different builds in different (sub-)directories.

Heh, same comes out if you mix up mkl linker commands..... Clean+rebuild is one of possibilities.

no idea, if you mix mingw and llvm files such link errors are expected. Just make as clean development tools install as possible.