| /oneTBB/include/oneapi/tbb/ |
| H A D | collaborative_call_once.h | 134 done, enumerator
171 set_completion_state(runner.to_bits(), state::done); in do_collaborative_call_once()
182 … } while (expected > state::done && !m_state.compare_exchange_strong(expected, expected + 1)); in do_collaborative_call_once()
195 } while (expected != state::done); in do_collaborative_call_once()
211 if (flag.m_state.load(std::memory_order_acquire) != collaborative_once_flag::done) { in collaborative_call_once()
|
| /oneTBB/test/conformance/ |
| H A D | conformance_task_arena.cpp | 40 std::atomic<bool> done{ false }; variable
42 a.enqueue([&done] { in __anon3e0b77410102()
44 done = true; in __anon3e0b77410102()
56 while (!done) {
|
| /oneTBB/examples/graph/binpack/ |
| H A D | binpack.cpp | 88 bool done; // flag to indicate that this binpacker has been deactivated member in bin_filler
98 done(false) {} in bin_filler()
102 if (done) in operator ()()
131 done = true; in operator ()()
137 done = true; in operator ()()
175 done = true; in operator ()()
|
| /oneTBB/doc/main/tbb_userguide/ |
| H A D | communicate_with_nodes.rst | 78 done, you need to call the function wait_for_all on both graphs.
83 g2. The call to g2.wait_for_all returns after both m1 and m2 are done,
86 reached before n1 and n2 are done.
99 // all tasks are done
105 between nodes in different graphs should be done with caution.
|
| H A D | Concurrent_Queue_Classes.rst | 13 The check and popping have to be done in a single operation for sake of
63 appropriate when the synchronization has to be done at a higher level.
|
| H A D | always_use_wait_for_all.rst | 10 useful when you want to wait until the computation is done, but it is
|
| H A D | cancel_a_graph.rst | 9 cancel_group_execution() on that object. This is done in the example
|
| H A D | use_concurrency_limits.rst | 31 as is done below:
|
| H A D | concurrent_hash_map.rst | 93 up that key in the table block until the ``accessor`` is done. A
|
| H A D | use_nested_flow_graphs.rst | 127 body to block until the inner graph is done. In the first implementation
|
| /oneTBB/ |
| H A D | INSTALL.md | 51 Installation can also be done using:
112 # Well done! Your installed oneTBB is in /tmp/my_installed_onetbb
134 REM Well done! Your installed oneTBB is in %TMP%\my_installed_onetbb
|
| H A D | README.md | 51 By its terms, contributions submitted to the project are also done under that license.
|
| /oneTBB/doc/main/tbb_userguide/design_patterns/ |
| H A D | Odd-Even_Communication.rst | 13 Operations on data cannot be done entirely independently, but data
|
| H A D | Reference_Counting.rst | 24 solution that extends to parallel programming if done carefully.
47 except that the increment/decrement is done atomically, and the
|
| H A D | Agglomeration.rst | 26 elementwise addition of two arrays can be done fully in parallel, but
37 - Individual computations can be done in parallel, but are small.
|
| H A D | Lazy_Initialization.rst | 72 is invoked when initialization has already been done.
|
| H A D | Non-Preemptive_Priorities.rst | 36 be done next that is *not* the default oneTBB rule.
|
| H A D | Fenced_Data_Transfer.rst | 132 done by another thread before it released a lock on that mutex.
|
| /oneTBB/src/tbb/ |
| H A D | private_server.cpp | 388 if (old <= 0) goto done; in wake_some()
392 done: in wake_some()
|
| H A D | queuing_rw_mutex.cpp | 300 goto done; in release()
407 done: in release()
|
| /oneTBB/test/tbb/ |
| H A D | test_flow_graph_priorities.cpp | 259 std::atomic<bool> done; member
267 while (!activity->done) { in operator ()()
278 void stop_and_wait() { done = true; my_service_thread.join(); } in stop_and_wait()
286 : done(false), my_service_thread(ServiceThreadFunc(barrier), this) {} in AsyncActivity()
|
| /oneTBB/python/rml/ |
| H A D | ipc_server.cpp | 967 if( old<=0 ) goto done; in wake_some()
982 done: in wake_some()
1013 if( old<=0 ) goto done; in wake_one_forced()
1026 done: in wake_one_forced()
|
| /oneTBB/doc/main/intro/ |
| H A D | limitations.rst | 20 * Compilation is done with Clang 12.0.0 or a more recent version.
|
| /oneTBB/doc/main/tbb_userguide/Migration_Guide/ |
| H A D | Task_API.rst | 262 In oneTBB this kind of recycling is done manually. You have to track when it is time to run the
367 In oneTBB, this can be done using ``oneapi::tbb::task_group``.
423 In oneTBB, this can be done using ``oneapi::tbb::task_group``.
|
| /oneTBB/cmake/compilers/ |
| H A D | GNU.cmake | 51 …# gcc 6.0 and later have -flifetime-dse option that controls elimination of stores done outside th…
|