3 ms·
More of the latter, from what I've skimmed at least. Cilk was a language originally developed for parallelism by MIT, they developed a Cilk Plus revision, and
by iheartmemcache 10y ago
More of the latter, from what I've skimmed at least.
Cilk was a language originally developed for parallelism by MIT, they developed a Cilk Plus revision, and it later adopted by Intel as Cilk++ (where they added more functionality and a few keywords). This is basically an OSS implementation of the language without all the "good stuff" that comes with the Intel Compiler. You get green threads (fibers in Intel's lexicon), an acceptable malloc which is swapped in thought appropriate, real threading (which marks off critical sections in the conventional fashion) as necessary, and the ability to use spawn/async (a conventional barrier-wait thinger).
They say "SIMD[check]" so in theory there are all of those AVX512 with the SIMD stuff (xmm0,16..ymm0-32? It's been a while since I've looked at the ISA) in here but I went through the code briefly and saw no reference to utilization of those registers. This page is really doing a real disservice to the language because where it really shines is in the tooling that integrates with the language. The Parallel Suite XE (priced around Visual Studio) lets you get some crazy-granular stuff for traditional number--crunching that GCC and LLVM doesn't produce (effectively leaving those registers unused). With ICC, to state the obvious, you get that functionality, as well as all the fantastic cluster analysis stuff. (n.b. VS with TPL does a not-too-bad-job at utilizing the AVX(edit: put in "AVR" originally ugh haha) subset of the ISA.)
edit: https://bitbucket.org/intelcilkruntime/intel-cilk-runtime/src/d1f3fb93f5ab5f1276c323f40891188717b7026a/runtime/config/x86/cilk-abi-vla.c?at=master&fileviewer=file-view-default https://bitbucket.org/intelcilkruntime/intel-cilk-runtime/sr... Yeah.. not too much processor specific stuff. In that dir, a few files showed the impl details of their threads which was just a conventional mov $1, rax; mov $2,rbx, blah blah. Nothing special. There are references to the 'special sauce' (vla references) left in the code from "if __INTEL__COMPILER__" macros, so I'm guessing it's just a copy-paste. Shame, it's a great language/toolset.