> -----Original Message-----
> From: gcc-patches-ow...@gcc.gnu.org [mailto:gcc-patches-
> ow...@gcc.gnu.org] On Behalf Of Andi Kleen
> Sent: Saturday, March 8, 2014 3:13 PM
> To: Iyer, Balaji V
> Cc: Tobias Burnus; Gerald Pfeifer; gcc-patches; Jakub Jelinek
> Subject: Re: [wwwdocs] RFC - mention Cilk Plus in the GCC 4.9 release notes
> 
> Andi Kleen <a...@firstfloor.org> writes:
> 
> > "Iyer, Balaji V" <balaji.v.i...@intel.com> writes:
> >>
> >> The sentence "Current only..." should be changed to something like this:
> >>
> >> Currently all the features except _Cilk_for has been implemented.
> >
> > It would be also good if the documentation mentioned that you have to
> > specify -lcilkrts
> 
> Also it would be good to specify exactly what parts of Cilk are supported
> currently. It's some what hard to figure out.
> 
> One trap I ran into (perhaps naively) is that I tried to use cilk_spawn (as
> documented in some tutorials) instead of _Cilk_spawn

_Cilk_spawn is the correct keyword. "cilk_spawn" can be used if the user 
includes <cilk/cilk.h> which has the following 3 lines (and that's the whole 
file)

#define cilk_spawn _Cilk_spawn
#define cilk_sync _Cilk_sync
#define cilk_for _Cilk_for


In Cilk there are basically 3 keywords: _Cilk_spawn, _Cilk_sync and _Cilk_for. 
_Cilk_for patch is still under review but _Cilk_spawn and _Cilk_sync keywords 
are supported.

> 
> -Andi

Reply via email to