Intel® Parallel Composer

Why does the available number of workers changes execution for a 1 cilk_spawn program?

While optimizing a matrix manipulation code in C, I used CilkPlus to spawn a thread to execute in parallel two functions that are data independent and somewhat computationally intensive. Cilk_spawn is used in only one place in the code as follows:

Run-time exit function

I would like to understand run-time execution in Cilk a little better. 
I have downloaded Intel Cilk run-time release (cilkplus-rtl-003365 - released 3-May-2013).

On 09/09/2013 I had asked a question seeking to figure out which is the last function executed before Cilk run-time ends assuming execution went without any problems.

Barry suggested to look at “__cilkrts_c_return_from_initial()” in scheduler.c  and indeed that was what I needed at that time.

Compile Cilk Plus GCC Runtime Libraries for Debug

Hello All,

I was wondering whether there was some way to modify the makefiles for the GCC build of Cilk Plus to keep the labels for debugging (i.e. compile with -g).  I am trying to get a fuller picture of how the runtime system works in order to possibly modify it


Thank you!


Intel® Parallel Composer abonnieren