<?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 opencl working in OpenCL* for CPU</title>
    <link>https://community.intel.com/t5/OpenCL-for-CPU/opencl-working/m-p/824949#M1167</link>
    <description>Hello Shweta Shree,&lt;BR /&gt;&lt;BR /&gt;This is made possible by the OpenCL ICD. It is documented at: &lt;A href="http://www.khronos.org/registry/cl/extensions/khr/cl_khr_icd.txt"&gt;http://www.khronos.org/registry/cl/extensions/khr/cl_khr_icd.txt&lt;/A&gt;, here's a quote:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE&gt;  &lt;I&gt;  This extension defines a simple mechanism through which the Khronos
    installable client driver loader (ICD Loader) may expose multiple 
    separate vendor installable client drivers (Vendor ICDs) for
    OpenCL.  An application written against the ICD Loader will be able to 
    access all cl_platform_ids exposed by all vendor implementations 
    with the ICD Loader acting as a demultiplexor.&lt;/I&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;You can read more details in the linked page and by googling "opencl icd".&lt;BR /&gt;&lt;BR /&gt;Eli&lt;BR /&gt;</description>
    <pubDate>Thu, 22 Sep 2011 12:53:22 GMT</pubDate>
    <dc:creator>Eli_Bendersky__Intel</dc:creator>
    <dc:date>2011-09-22T12:53:22Z</dc:date>
    <item>
      <title>opencl working</title>
      <link>https://community.intel.com/t5/OpenCL-for-CPU/opencl-working/m-p/824948#M1166</link>
      <description>Can anyone please explain to me how a system handles 2 implementations of opencl.&lt;BR /&gt;(For example: intel and nvidia implementations).&lt;BR /&gt;&lt;BR /&gt;How appropriate backend compilers are used in the function clProgramBuild()?</description>
      <pubDate>Thu, 22 Sep 2011 12:16:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/OpenCL-for-CPU/opencl-working/m-p/824948#M1166</guid>
      <dc:creator>Shweta_Shree</dc:creator>
      <dc:date>2011-09-22T12:16:06Z</dc:date>
    </item>
    <item>
      <title>opencl working</title>
      <link>https://community.intel.com/t5/OpenCL-for-CPU/opencl-working/m-p/824949#M1167</link>
      <description>Hello Shweta Shree,&lt;BR /&gt;&lt;BR /&gt;This is made possible by the OpenCL ICD. It is documented at: &lt;A href="http://www.khronos.org/registry/cl/extensions/khr/cl_khr_icd.txt"&gt;http://www.khronos.org/registry/cl/extensions/khr/cl_khr_icd.txt&lt;/A&gt;, here's a quote:&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;PRE&gt;  &lt;I&gt;  This extension defines a simple mechanism through which the Khronos
    installable client driver loader (ICD Loader) may expose multiple 
    separate vendor installable client drivers (Vendor ICDs) for
    OpenCL.  An application written against the ICD Loader will be able to 
    access all cl_platform_ids exposed by all vendor implementations 
    with the ICD Loader acting as a demultiplexor.&lt;/I&gt;&lt;/PRE&gt;&lt;BR /&gt;&lt;BR /&gt;You can read more details in the linked page and by googling "opencl icd".&lt;BR /&gt;&lt;BR /&gt;Eli&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Sep 2011 12:53:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/OpenCL-for-CPU/opencl-working/m-p/824949#M1167</guid>
      <dc:creator>Eli_Bendersky__Intel</dc:creator>
      <dc:date>2011-09-22T12:53:22Z</dc:date>
    </item>
  </channel>
</rss>

