I'm having problems shutting down a task arena while there are tasks running into it. The specific problem I have is that I hit a TBB assert while I'm trying to shutdown and an already-existing task is trying to enque other work into the same arena.
The program has the following requirements with respect to the task arena:
I am attempting to use TBB and an OpenCL enabled FPGA. However, I am running into the following error:
"Error: Global work offset has been specified. That is an OpenCL 1.1 feature not supported by this version of the Intel(R) FPGA SDK for OpenCL(TM)
Failed to enqueue a kernel; error code: -56
TBB Warning: Exact exception propagation is requested by application but the linked library is built without support for it
terminate called after throwing an instance of 'tbb::captured_exception'
what(): Unidentified exception
Aborted (core dumped)"
What is the canonical way to tell a cmake-using library that normally links against libtbb to link against libtbb_preview instead?
Alternatively, is there a way to detect when a program or library tries to link to two incompatible versions of libtbb (like libtbb and libtbb_preview)?
I would like to convert code to tbb but i have problem set local variable private(x1,y1,sum) and shared variable on openmp to TBB .
I am trying to compile my C++ 14 code with Clang++ 5.0.0 on GNU/Linux using TBB 2018 update 1. Everything works fine with g++ 7.2.0 and Intel C++ Compiler 18, but when I try to switch to Clang++, it compiles but it crashes when I try to run it. Even, a simple hello world appliccation crashes when link it with TBB.
I am using the following module for detecting TBB from my system with cmake 3.9.3. The error is the following:
When I run it from terminal:
You have release TBB 2018 U1. Unfortunately my graph flow program does not link any more. I downgrade to TBB 2017 U6.
Did you update the API of TBB graph flow ?
We are trying to verify some of our programs that use TBB for data races using ThreadSanitizer data race detector (https://clang.llvm.org/docs/ThreadSanitizer.html). However, currently we are seeing lots of data race reports inside of TBB library itself which makes further verification impossible. See below for examples. The root problem is that TBB uses home-grown implementation of atomic operations which is not understood by ThreadSanitizer.