Binary versions of the GNU Compiler Collection (GCC) C and C++ 4.8 compilers with the cilkplus extension are now available from http://www.cilkplus.org/download#gcc-development-branch . The binaries support the x86-32 and x86-64 architectures on Ubuntu* Linux*. The source for these compilers is available at http://gcc.gnu.org/svn/gcc/branches/cilkplus-4_8-branch .
We are pleased to announce an update to the Intel® Cilk™ Plus Language Specification. This document describes the syntax and semantics of the Cilk™ Plus language constructs that were added to the C and C++ programming languages. This version of the specification was relseased in September, 2013 and supersedes the 1.1 version of the same specification released in July, 2011. This version adds no new features to the language extensions described in the V1.1 specification, but contains numerous corrections and clarifications. A few obsolete constructs were removed.
We are pleased to announce that Cilkpub, a library of community-contributed Cilk Plus code, is now available for download.
Cilkpub is intended to be a public library of code contributed and maintained by the members of the Cilk Plus community. Version 1.02 has been posted to the community website and contains the following modules:
Check out the new Intel® Cilk Plus™ website http://cilkplus.org/. Learn about the latest product information, download tools and samples, submit contributions, and much more!
If you have any comments or suggestions, we would love to hear them.
The Intel Cilk Plus SDK (Software Development Kit) is now available as a WhatIf kit. It supplies the Cilkscreen race detection and Cilkview scalability tools for Intel Cilk Plus developers working on the Microsoft Windows* and Linux* operating systems.
More information can be found at the Intel Cilk Plus Download page. Support for the Intel Cilk Plus SDK will be provided through the Intel Cilk Plus forum.
What I understood about steal-continuation is, that every idle thread does not actually steal work, but the continuation which generates a new working item.
Does that mean, that inter-spawn execution time is crucial? If 2 threads are idle at the same time, from what I understand only one can steal the continuation and create its working unit, the other thread stays idle during that time?!
As a debugging artefact, I had a global counter incremented on every function call of a function used within every working item.
I'm new to cilk, and i wanted to ask if it has an implicit threshold for the task creation, in recursive computations like fib?
If so, is it based on the number of tasks created, or in the depth of the computation?
I have code that is structured like this:
I'm having difficulty running a simple test case using cilk_spawn. I'm compiling under gcc 4.9.0 20130520.
The following fib2010.cpp example, executes in 0.028s without cilk and takes 0.376s with cilk as long as I set the number of workers to 1. If I change the number of workers to any number greater than one, I get a segmentation fault.
- Page 1