Intel® Threading Building Blocks

Intel® Parallel Studio XE 2016 Beta program has started!

The Intel® Parallel Studio XE 2016 Beta program is now available!

In this beta test, you will have early access to Intel® Parallel Studio XE 2016 products and the opportunity to provide feedback to help make our products better. Registration is easy through the pre-Beta survey site.

This suite of products brings together exciting new technologies along with improvements to Intel’s existing software development tools:

Mac install location conflicts with code signing

tbb dylibs on the Mac are built with an install name path (otool -D) of "libtbb.dylib" (and similar names for all the other tbb libraries), which means that if you link with them as-is and place it inside an app package in the Apple-recommended location, they won't be found and you'll die on launch with

dyld: Library not loaded: libtbb_debug.dylib

  Referenced from: /Users/williams/photoshop/main/photoshop/Targets/Debug_x86_64/Adobe Photoshop CC Photoshop CC 2015

  Reason: image not found

class hierarchy for FlowGraph nodes

Apology's up front if this turns out to be a stupid question: I'm getting my head in a right old tangle with the template functions...

I'm trying to design a reconfigurable flowgraph framework: whereby the actual makeup of the flowgraph can be dynamically created at runtime (from a configuration file). The flowgraph would consist of:

- function_node

- multifunction_node

- source_node

- join_node (working in conjunction with a function_node).

There is only a single datatype flowing through all of these nodes, lets call it CDataClass*.

calling flowgraph operators()() through shared library

Does anyone know if this is possible?...

To create a FlowGraph whereby each function is a class loaded from a shared library: probably Boost::extension to maintain portability between Windows & Linux.

Just a little concerned about:

- calls to the operator() to run the flow graph function

- any performance penalties this may incur

Any ideas?



S’abonner à Intel® Threading Building Blocks