Searched refs:completed (Results 1 – 9 of 9) sorted by relevance
| /oneTBB/test/conformance/ |
| H A D | conformance_task_group.cpp | 144 bool completed {false}; variable 149 completed = true; in __anon0c2008c70602() 153 …CHECK_MESSAGE(completed == false, "Deferred task should not be run until run(task_handle) is calle… in __anon0c2008c70702() 159 … CHECK_MESSAGE(completed == true, "Deferred task should be completed when task_group::wait exits"); in __anon0c2008c70702() 164 …CHECK_MESSAGE(completed == false, "Deferred task should not be run until run(task_handle) is calle… 169 …CHECK_MESSAGE(completed == false, "Deferred task should not be run until run(task_handle) and wait…
|
| /oneTBB/test/tbb/ |
| H A D | test_task_arena.cpp | 933 std::atomic<int>& completed; member in TestIsolatedExecuteNS::TestEnqueueTask 947 ++completed; in execute() 959 std::atomic<int>& completed; member in TestIsolatedExecuteNS::TestEnqueueIsolateBody 965 : executed(exe), completed(c), arena(a) {} in TestEnqueueIsolateBody() 977 std::atomic<int> completed; in TestEnqueue() local 981 completed = 0; in TestEnqueue() 982 TestEnqueueIsolateBody b1(executed, completed, arena); in TestEnqueue() 990 completed = 0; in TestEnqueue() 999 ++completed; in TestEnqueue() 1773 bool completed{ false }; in test_threads_sleep() local [all …]
|
| H A D | test_task_group.cpp | 200 …RunAndWaitSyncronizationTestBody(utils::SpinBarrier& barrier, std::atomic<bool>& completed, task_g… in RunAndWaitSyncronizationTestBody() argument 201 : m_barrier(barrier), m_completed(completed), m_tg(tg) {} in RunAndWaitSyncronizationTestBody() 230 std::atomic<bool> completed; in TestParallelWait() local 231 completed = false; in TestParallelWait() 233 RunAndWaitSyncronizationTestBody<task_group_type> b(barrier, completed, tg); in TestParallelWait()
|
| /oneTBB/doc/main/tbb_userguide/ |
| H A D | Initializing_and_Terminating_the_Library.rst | 16 until all worker threads implicitly created by the library have completed.
|
| H A D | Task_Scheduler_Bypass.rst | 11 - Continue to execute the current task until it is completed.
|
| H A D | How_Task_Scheduler_Works.rst | 24 …Also, if they can be completed, tasks that depend on it can continue executing, and though not the…
|
| /oneTBB/doc/main/tbb_userguide/design_patterns/ |
| H A D | Local_Serializer.rst | 97 * - Any prior work for the ``Serializer`` has completed. 183 #. Notify the ``Serializer`` that the functor completed, and thus
|
| H A D | Wavefront.rst | 59 known, treat this conceptual predecessor as completed.
|
| /oneTBB/doc/main/tbb_userguide/Migration_Guide/ |
| H A D | Task_API.rst | 227 Such patterns are particularly useful when the work within a functor is not completed but there is a
|