Intel® Threading Building Blocks

What's New? Intel® Threading Building Blocks 2017 Update 3

Changes (w.r.t. Intel TBB 2017 Update 2):

- Added support for Android* 7.0 and Android* NDK r13, r13b.

Preview Features:

- Added template class gfx_factory to the flow graph API. It implements
    the Factory concept for streaming_node to offload computations to
    Intel(R) processor graphics.

Bugs fixed:

- Fixed a possible deadlock caused by missed wakeup signals in

Heterogeneous TBB (flow graph promotion): 

  • C/C++
  • Intel® Threading Building Blocks
  • Invoking parallel_for while holding a lock


    The following code does not finish (mostly on my system). Am I doing something I shouldn't do? (i.e. invoking parallel_for while holding a lock) I think if parallel_for is invoked while all the other workers are blocked, the parallel_for routine should be executed single-threaded but it seems like this is not what's happening...

    tbb::concurrent_lru_cache design

    I'm using the concurrent_lru_cache and generally like it, but it appears that there is no possibility for the callback function to fail: operator[] allocates a new bucket and calls the function that produce the value if is_new_value_needed() returns true.

    So far, so good, but what if the function fails? It cannot throw an exception as any other thread waiting on that cache slot will now spin forever.

    借助 SIMD 数据布局模板优化数据布局

    Financial service customers need to improve financial algorithmic performance for models such as Monte Carlo, Black-Scholes, and others. SIMD programming can speed up these workloads. In this paper, we perform data layout optimizations using two approaches on a Black-Scholes workload for European options valuation from the open source Quantlib library.
  • Modern Code
  • C/C++
  • Intermediate
  • Intel® C++ Compiler
  • Intel® Threading Building Blocks
  • SDLT
  • QuantLib*
  • Financial Services Industry
  • Unicode stiil compile error

    I compiled the latest libtbb (also tbbmalloc and tbbmalloc_proxy) with VS2013 on Win10 x64 in Unicode mode. It failed with several errors, such as "const char* type is not compatible with const unicode_char_t*" in line 632 proxy.cpp.  I just wound why macro _T or _TEXT was not used to realize unicode support, or you can just use char* and functions appended with 'A' to avoid these problems. By the way, a semicolon missed in line 601 proxy.cpp.

    Subscribe to Intel® Threading Building Blocks