| /oneTBB/doc/main/tbb_userguide/ |
| H A D | Task_Scheduler_Bypass.rst | 8 the spawning of the new task to be executed by the current thread involves the next steps:
15 … using "Task Scheduler Bypass" technique to directly point the preferable task to be executed next
17 the returned task becomes the first candidate for the next task to be executed by the thread. Furth…
18 the task is executed by the current thread and not by any other thread.
|
| H A D | estimate_flow_graph_performance.rst | 27 in your graph if executed sequentially. Then let C be the time
30 Therefore, even if all other paths are executed in parallel with C,
|
| H A D | Flow-Graph-exception-tips.rst | 9 optionally reset the graph so that it can be re-executed.
|
| H A D | Floating_Point_Settings.rst | 6 To propagate CPU-specific settings for floating-point computations to tasks executed by the task sc…
41 * Floating-point settings are applied to all tasks executed within a task arena, if they are captur…
|
| H A D | Bandwidth_and_Cache_Affinity_os.rst | 28 - The loop, or a similar loop, is re-executed over the same data.
60 each iteration can be handed to the same thread that executed it before.
|
| H A D | attach_flow_graph_to_arena.rst | 27 the task arena instance, inside which the ``graph::reset()`` method is executed.
|
| H A D | Containers.rst | 47 the operation to be executed on an undefined object.
|
| H A D | Exceptions_and_Cancellation.rst | 16 #. The algorithm is cancelled. Pending iterations are not executed. If
|
| H A D | Mapping_Nodes2Tasks.rst | 51 execute all of the tasks that can be executed in parallel. If there are
|
| H A D | Parallelizing_Flow_Graph.rst | 91 choose at runtime what will be executed in parallel.
|
| H A D | Dependence_Graph.rst | 137 execute all of the tasks that can be executed concurrently in parallel.
|
| H A D | std_invoke.rst | 70 …the algorithm's body. This Function Object defined the operations to be executed on each iteration…
|
| /oneTBB/doc/main/reference/ |
| H A D | task_group_extensions.rst | 63 As an optimization hint, ``F`` might return a ``task_handle``, which task object can be executed ne…
70 As an optimization hint, ``F`` might return a ``task_handle``, which task object can be executed ne…
78 As an optimization hint, ``F`` might return a ``task_handle``, which task object can be executed ne…
|
| /oneTBB/include/oneapi/tbb/detail/ |
| H A D | _utils.h | 255 executed, ///< Do-once routine has been executed enumerator
256 initialized = executed ///< Convenience alias
275 while ( state.load( std::memory_order_acquire ) != do_once_state::executed ) { in atomic_do_once()
296 state.store(do_once_state::executed, std::memory_order_release); in atomic_do_once()
|
| /oneTBB/test/conformance/ |
| H A D | conformance_graph.cpp | 293 std::atomic<unsigned> executed(0); variable
295 ++executed; in __anon8ef3c1da0202()
305 while( !executed ) in __anon8ef3c1da0302()
313 CHECK_MESSAGE(1 == executed, "Buffered messages should be dropped by the cancelled graph." );
|
| /oneTBB/test/tbb/ |
| H A D | test_task_arena.cpp | 932 tbb::enumerable_thread_specific<bool>& executed; member in TestIsolatedExecuteNS::TestEnqueueTask
941 : executed(exe), completed(c), waiter(w), arena(a) {} in TestEnqueueTask()
946 executed.local() = true; in execute()
958 tbb::enumerable_thread_specific<bool>& executed; member in TestIsolatedExecuteNS::TestEnqueueIsolateBody
965 : executed(exe), completed(c), arena(a) {} in TestEnqueueIsolateBody()
976 tbb::enumerable_thread_specific<bool> executed(false); in TestEnqueue() local
982 TestEnqueueIsolateBody b1(executed, completed, arena); in TestEnqueue()
985 if (!executed.local()) { in TestEnqueue()
989 executed.local() = false; in TestEnqueue()
998 executed.local() = true; in TestEnqueue()
[all …]
|
| /oneTBB/doc/main/tbb_userguide/Migration_Guide/ |
| H A D | Task_API.rst | 333 TBB ``task::execute()`` method can return a pointer to a task that can be executed next by the curr…
335 is not guaranteed to be executed next by the current thread.
419 // Control flow will reach here only after both ChildTask and CallBackTask are executed,
444 // Control flow gets here once both ChildTask and CallBackTask are executed
453 ``CallBackTask`` are executed.
|
| /oneTBB/doc/GSG/ |
| H A D | intro.rst | 11 to be executed simultaneously. Using threads can make your program work faster and more efficiently.
|
| /oneTBB/integration/windows/oneapi/ |
| H A D | vars.bat | 20 echo :: ERROR: This script must be executed by setvars.bat.
|
| /oneTBB/cmake/toolchains/ |
| H A D | mips.cmake | 31 # It can't be executed on host system in case of cross-compilation for MIPS architecture.
|
| /oneTBB/doc/main/tbb_userguide/design_patterns/ |
| H A D | GUI_Thread.rst | 70 The following figure sketches the communication paths. Items in black are executed
71 by the GUI thread; items in blue are executed by another thread.
|
| H A D | Fenced_Data_Transfer.rst | 152 Another mistake is to assume that conditionally executed code cannot
|
| /oneTBB/ |
| H A D | LICENSE.txt | 135 the terms of any separate license agreement you may have executed
|