threadman

1. Cilk++ has nested parallelism that works and provides guaranteed speed-up. OpenMP has nested parallelism, but it is a memory hog and not reliable.

2. Cilk++ guarantees space bounds. On P processors, Cilk++ uses no more than P times the stack space of a serial execution. In OpenMP, not so.

3. Cilk++ has a race detector for debugging and software release. With OpenMP, you are on your own.

4. Cilk++ has serial semantics. With OpenMP, you do not have this benefit – only a subset of OpenMP supports serial semantics.

5. Cilk++ has a solution for global variables (a construct called "hyperobjects"). OpenMP does not.

sorry, I'm not clear- do you mean you distribute it under GPL2, or that GPL2 allows use without releasing the resulting work?

do you distribute your work under GPL? If so, then you wouldn't see a change under CAPL.

Here's the (alpha) documentation and code samples: http://www.cilk.com/resources-for-multicoders/for-developers...

Here's the (alpha) documentation and code samples: http://www.cilk.com/resources-for-multicoders/for-developers...

TBB borrows the scheduling portion, but requires substantial code restructuring, and doesn't have a solution for the global variable problem analogous to Cilk's hyperobjects.

interesting point - worth a comment in the blog post

Does the following help? (A link to the alpha documentation.) http://www.cilk.com/resources-for-multicoders/documentation-...

We will post a bunch of code examples as well, but wanted to get something up sooner than later.

thank you.

Cilk++ is a considerable upgrade to MIT Cilk: support for C++ (rather than just C), for Visual Studio (rather than just GCC), support for loops (rather than just recursion). It's considerably more transparent to the developer.

so let's say the team actually wants to target developers rather than suits - what are the key things you'd change about the web site?

thanks in advance.