| /oneTBB/test/common/ |
| H A D | utils_assert.h | 29 void ReportError( const char* filename, int line, const char* expression, const char * message ) { in ReportError() argument 31 …REPORT_FATAL_ERROR("%s:%d, assertion %s: %s\n", filename, line, expression, message ? message : "f… in ReportError() 36 …== _CrtDbgReport(_CRT_ASSERT, filename, line, nullptr, "%s\r\n%s", expression, message?message:"")) in ReportError() 49 #define ASSERT_CUSTOM(p,message,file,line) ((p)?(void)0:utils::ReportError(file,line,#p,message)) argument 50 #define ASSERT(p,message) ASSERT_CUSTOM(p,message,__FILE__,__LINE__) argument
|
| /oneTBB/doc/main/tbb_userguide/ |
| H A D | Flow_Graph_Buffering_in_Nodes.rst | 9 message successfully to any successor, no further action is taken with 10 the message by that node. As noted in the section on Single-push vs. 11 Broadcast-push, a message may be passed to one or to multiple 13 connected to the node, and whether the message is pushed or pulled. 16 There are times when a node cannot successfully push a message to any 17 successor. In this case what happens to the message depends on the type 21 - The node stores the message to be forwarded later. 22 - The node discards the message. 30 If a message has been stored by a node, there are two ways it can be 34 - A successor to the node can pull the message using ``try_get()`` or [all …]
|
| H A D | Flow_Graph_Message_Passing_Protocol.rst | 9 message from its predecessor. For a graph to operate most-efficiently, 11 state to pull so when the successor is able to handle a message it can 12 query its predecessor to see if a message is available. If the edge did 14 repeatedly attempt to forward its message until the successor accepts 19 try to pull a message from a predecessor. 22 #. If a predecessor has a message, the successor will process it and the 24 #. If the predecessor has no message, the edge between the nodes will
|
| H A D | Flow_Graph_Reservation.rst | 10 every input before they can create an output message. The reserving 12 messages from its inputs until it has a message at each input. To create 13 an output message it temporarily reserves a message at each input port, 15 message be created. If any input port fails to reserve a message, no 16 message will be pulled by the ``join_node``. 24 tries to push a message, the ``join_node`` always rejects the push 32 reserving ``join_node`` will create a message using the reserved 35 - If the message is successfully pushed to a successor, the 39 - If the message was not successfully pushed to any successor, the 47 to create and push a message if all input ports succeed reserving [all …]
|
| H A D | Nodes.rst | 9 both. A node performs some operation, usually on an incoming message and 11 one input message or generate more than one output message. 45 …r lambda expression, that is applied to the incoming message to generate the outgoing message. … 96 concurrency limit of 1. When it receives the message sequence 1, 2 and 102 immediately spawn a task to process the message, the message will be 104 task will be spawned to process the next buffered message. 107 In the above graph, each message is processed sequentially. If however, 124 to spawn a task as soon as a message arrives, regardless of how many
|
| H A D | broadcast_or_send.rst | 67 In the above example, each message buffered by the priority_queue_node 73 all, nodes accept a message? Should the message be buffered until all 75 node continues to buffer the message, should it eventually deliver the 77 at the time the node accepts the next message? For example, assume a 82 ensure that all successors receive each message creates a garbage 84 nodes push each message to only one successor. And, you can use this 86 in the graph above, where each message will be processed in priority
|
| H A D | Predefined_Node_Types.rst | 35 …- A single-input, single-output node that broadcasts each message received to all successors. I… 39 …e output type is a tuple of these generic types. The node combines one message from each input p… 43 …message and broadcast their outputs to all successors. After broadcast, the nodes retain the … 45 …ric type. The node increments an internal counter when it broadcasts a message. If the increment… 47 …message to all of its successors. The input type is a list of generic types and the output type … 51 … messages of generic type, invokes the user-provided body to submit a message to an external ac…
|
| H A D | Flow_Graph_Single_Vs_Broadcast.rst | 13 are able to accept a message, each message will be only sent to one 15 - **broadcast-push**: A message will be pushed to every successor which 17 the message. 101 message it receives to all accepting successors. Putting three messages
|
| H A D | communicate_with_nodes.rst | 70 In the example above, m1.try_put(1) sends a message to node m1, which 71 runs its body and then sends a message to node m2. Next, node m2 runs 72 its body and sends a message to n1 using an explicit try_put. In turn, 73 n1 runs its body and sends a message to n2. The runtime library does not
|
| H A D | use_limiter_node.rst | 24 allowed to pass. When a message leaves the controlled part of the graph, 25 a message can be sent to the decrement port on the ``limiter_node`` to 78 reaches 3. When the ``input_node`` sees its message rejected, it stops
|
| H A D | use_input_node.rst | 50 it might send a message to squarer immediately after the edge to 107 made first, ``func1`` might generate a message before ``func2`` is attached to 108 it; that message would be dropped. Also, src has only a single
|
| /oneTBB/include/oneapi/tbb/detail/ |
| H A D | _assert.h | 44 …ASSERT_RELEASE(predicate,message) ((predicate)?((void)0) : rml::internal::assertion_failure(__func… argument 46 …SSERT_RELEASE(predicate,message) ((predicate)?((void)0) : tbb::detail::r1::assertion_failure(__fun… argument 54 #define __TBB_ASSERT(predicate,message) __TBB_ASSERT_RELEASE(predicate,message) argument
|
| /oneTBB/examples/parallel_for/seismic/ |
| H A D | seismic_video.cpp | 62 LRESULT CALLBACK WndProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam); 101 LRESULT CALLBACK About(HWND hDlg, UINT message, WPARAM wParam, LPARAM lParam) { in About() argument 102 switch (message) { in About() 114 LRESULT CALLBACK WndProc(HWND hWnd, UINT message, WPARAM wParam, LPARAM lParam) { in WndProc() argument 116 switch (message) { in WndProc() 130 default: return DefWindowProc(hWnd, message, wParam, lParam); in WndProc() 133 default: return DefWindowProc(hWnd, message, wParam, lParam); in WndProc()
|
| /oneTBB/test/conformance/ |
| H A D | conformance_sequencer_node.cpp | 139 using message = conformance::sequencer_functor<int>::seq_message; typedef 143 function_node<message, message> process(g, unlimited, [] (message msg) { in __anona3025c380302() 148 sequencer_node<message> ordering(g, conformance::sequencer_functor<int>()); 151 function_node<message> writer(g, tbb::flow::serial, [&] (const message& msg) { in __anona3025c380402() 159 message msg = {i, 0};
|
| H A D | conformance_flowgraph.h | 45 struct message { struct 48 message(int _data) : data(_data) {}; in message() argument 51 message(){}; in message() function 54 message(const message& msg) : data(msg.data) {}; in message() function 57 message& operator=(const message& msg) { 66 bool operator==(const message& msg) const {
|
| H A D | conformance_async_node.cpp | 27 using input_msg = conformance::message</*default_ctor*/true, /*copy_ctor*/true, /*copy_assign*/fals… 28 using output_msg = conformance::message</*default_ctor*/false, /*copy_ctor*/false, /*copy_assign*/f…
|
| /oneTBB/src/tbbmalloc/ |
| H A D | Customize.h | 21 #define MALLOC_ASSERT(assertion, message) __TBB_ASSERT(assertion, message) argument 22 #define MALLOC_ASSERT_EX(assertion, message) __TBB_ASSERT_EX(assertion, message) argument
|
| /oneTBB/doc/main/reference/ |
| H A D | type_specified_message_keys.rst | 3 Type-specified message keys for join_node 42 ``key_from_message`` function for each incoming message to obtain the key associated 61 By default, the ``key()`` method defined in the message class will be called. 63 same namespace with the message type. This function will be found via C++ argument-dependent
|
| /oneTBB/cmake/android/ |
| H A D | environment.cmake | 19 message(FATAL_ERROR "Could not find adb") 25 message(FATAL_ERROR "Error while on device execution: ${cmd} error_code: ${CMD_RESULT}") 33 message(FATAL_ERROR "Error while data transferring: ${data_path} error_code: ${CMD_RESULT}")
|
| /oneTBB/cmake/python/ |
| H A D | test_launcher.cmake | 21 message(FATAL_ERROR "Cannot find oneTBB Python module") 23 …message(WARNING "Found more than oneTBB Python modules, the only first found module will be tested… 37 message(FATAL_ERROR "Error while test execution: ${cmd} error_code: ${CMD_RESULT}")
|
| /oneTBB/ |
| H A D | CMakeLists.txt | 29 …message(FATAL_ERROR "CMAKE_MSVC_RUNTIME_LIBRARY was defined while policy CMP0091 is not available.… 33 …message(FATAL_ERROR "Enabled TBB_WINDOWS_DRIVER requires CMAKE_MSVC_RUNTIME_LIBRARY to be set to M… 79 … message(FATAL_ERROR "C++${CMAKE_CXX_STANDARD} (${TBB_CXX_STD_FLAG}) support is required") 119 …message(WARNING "You are building oneTBB as a static library. This is highly discouraged and such … 124 message(STATUS "CMAKE_BUILD_TYPE is not specified. Using default: ${CMAKE_BUILD_TYPE}") 222 message(STATUS "IPO enabled") 230 message(WARNING "TBB compiler settings not found ${TBB_COMPILER_SETTINGS_FILE}") 236 message(STATUS "Using external TBB for testing") 249 message(STATUS "TBBBind build targets are disabled due to unsupported environment") 299 message(FATAL_ERROR "Benchmarks are not supported yet")
|
| /oneTBB/doc/main/tbb_userguide/design_patterns/ |
| H A D | Fenced_Data_Transfer.rst | 13 Write a message to memory and have another processor read it on 32 write a message and mark it as ready to ready as shown in the 52 return result; // Return true if message was received. 88 that indicates when the message is ready. Here is the previous 108 return result; // Return true if message was received.
|
| /oneTBB/examples/common/gui/ |
| H A D | CMakeLists.txt | 44 message(FATAL_ERROR 71 message(FATAL_ERROR "Cannot find the DirectX library (required by the 'd2d' UI mode)") 93 message(FATAL_ERROR "Cannot find the Foundation library (required by the 'mac' UI mode)") 98 message(FATAL_ERROR "Cannot find the Cocoa library (required by the 'mac' UI mode)")
|
| /oneTBB/cmake/templates/ |
| H A D | TBBConfig.cmake.in | 112 message(STATUS "Missed required oneTBB component: ${_tbb_component}") 114 message(STATUS " ${_tbb_release_lib} must exist.") 116 …message(STATUS " one or both of:\n ${_tbb_release_lib}\n ${_tbb_debug_lib}\n files must ex…
|
| /oneTBB/src/tbbbind/ |
| H A D | CMakeLists.txt | 19 message(STATUS "HWLOC target ${REQUIRED_HWLOC_TARGET} doesn't exist." 98 …message(STATUS "The ${TBBBIND_LIBRARY_NAME} target will be configured using the HWLOC ${HWLOC_VERS…
|