<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic I don't think Clik(tm) Plus  in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Open-CL-vs-CILK/m-p/972240#M24246</link>
    <description>&lt;P&gt;I don't think Clik(tm) Plus (if you mean Intel's implementation) and OpenCL are suited to the same projects.&lt;/P&gt;
&lt;P&gt;OpenCL was put forward as a way to support compatibility with applicatations architectures where C++ isn't suitable, not so much as a performance competitive alternative to Intel compilers.&lt;/P&gt;
&lt;P&gt;It's in a relative early stage of development.&amp;nbsp; It seems LLVM has only recently been attempting to catch up&amp;nbsp; to gcc in performance.&amp;nbsp; In part, Intel's claim to higher performance than gcc has been based on more aggressive default options, the use of #pragma optimization directives, and the performance libraries provided with Intel C++.&amp;nbsp;&amp;nbsp; The latter would appear to be important for your area of interest.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 25 May 2013 12:52:11 GMT</pubDate>
    <dc:creator>TimP</dc:creator>
    <dc:date>2013-05-25T12:52:11Z</dc:date>
    <item>
      <title>Open CL vs. CILK</title>
      <link>https://community.intel.com/t5/Software-Archive/Open-CL-vs-CILK/m-p/972239#M24245</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;It seems CILK is much easier to use than Open CL.&lt;/P&gt;
&lt;P&gt;Do you have any information of the performance of CILK vs. Open CL on the same machine (e.g Intel's Ivy-Bridge) ?&lt;/P&gt;
&lt;P&gt;Does it depend on the what I'm trying to do ?&lt;/P&gt;
&lt;P&gt;My interest is&amp;nbsp;Signal Processing (FFT, matrix manipulation etc.) &amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Zvika&lt;/P&gt;</description>
      <pubDate>Sat, 25 May 2013 06:47:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Open-CL-vs-CILK/m-p/972239#M24245</guid>
      <dc:creator>Zvi_Vered</dc:creator>
      <dc:date>2013-05-25T06:47:15Z</dc:date>
    </item>
    <item>
      <title>I don't think Clik(tm) Plus</title>
      <link>https://community.intel.com/t5/Software-Archive/Open-CL-vs-CILK/m-p/972240#M24246</link>
      <description>&lt;P&gt;I don't think Clik(tm) Plus (if you mean Intel's implementation) and OpenCL are suited to the same projects.&lt;/P&gt;
&lt;P&gt;OpenCL was put forward as a way to support compatibility with applicatations architectures where C++ isn't suitable, not so much as a performance competitive alternative to Intel compilers.&lt;/P&gt;
&lt;P&gt;It's in a relative early stage of development.&amp;nbsp; It seems LLVM has only recently been attempting to catch up&amp;nbsp; to gcc in performance.&amp;nbsp; In part, Intel's claim to higher performance than gcc has been based on more aggressive default options, the use of #pragma optimization directives, and the performance libraries provided with Intel C++.&amp;nbsp;&amp;nbsp; The latter would appear to be important for your area of interest.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 25 May 2013 12:52:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Open-CL-vs-CILK/m-p/972240#M24246</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2013-05-25T12:52:11Z</dc:date>
    </item>
  </channel>
</rss>

