<?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 How to protect OpenCL kernel code? in OpenCL* for CPU</title>
    <link>https://community.intel.com/t5/OpenCL-for-CPU/How-to-protect-OpenCL-kernel-code/m-p/1070964#M4435</link>
    <description>&lt;P&gt;&amp;nbsp; &amp;nbsp; I use OpenCL for &amp;nbsp;integrated GPU. &amp;nbsp;Everything is ready, except how to protect kernel code. I know this is an old topic.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp; &amp;nbsp; I have tried to translate the kernel code to SPIR code. but anybody can get II code through SPIR , using llvm-dsi. &amp;nbsp;Because integrated GPUs &amp;nbsp;only support OpenCL1.2, GPU can't use SPIR-V code. So is there a better way to protect kernel code?&lt;/P&gt;</description>
    <pubDate>Tue, 01 Nov 2016 09:14:54 GMT</pubDate>
    <dc:creator>QQ_Q_</dc:creator>
    <dc:date>2016-11-01T09:14:54Z</dc:date>
    <item>
      <title>How to protect OpenCL kernel code?</title>
      <link>https://community.intel.com/t5/OpenCL-for-CPU/How-to-protect-OpenCL-kernel-code/m-p/1070964#M4435</link>
      <description>&lt;P&gt;&amp;nbsp; &amp;nbsp; I use OpenCL for &amp;nbsp;integrated GPU. &amp;nbsp;Everything is ready, except how to protect kernel code. I know this is an old topic.&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp; &amp;nbsp; I have tried to translate the kernel code to SPIR code. but anybody can get II code through SPIR , using llvm-dsi. &amp;nbsp;Because integrated GPUs &amp;nbsp;only support OpenCL1.2, GPU can't use SPIR-V code. So is there a better way to protect kernel code?&lt;/P&gt;</description>
      <pubDate>Tue, 01 Nov 2016 09:14:54 GMT</pubDate>
      <guid>https://community.intel.com/t5/OpenCL-for-CPU/How-to-protect-OpenCL-kernel-code/m-p/1070964#M4435</guid>
      <dc:creator>QQ_Q_</dc:creator>
      <dc:date>2016-11-01T09:14:54Z</dc:date>
    </item>
    <item>
      <title>This article has more details</title>
      <link>https://community.intel.com/t5/OpenCL-for-CPU/How-to-protect-OpenCL-kernel-code/m-p/1070965#M4436</link>
      <description>&lt;P&gt;This article has more details on the options available today:&lt;/P&gt;

&lt;P&gt;&lt;A href="https://software.intel.com/en-us/articles/using-spir-for-fun-and-profit-with-intel-opencl-code-builder"&gt;https://software.intel.com/en-us/articles/using-spir-for-fun-and-profit-with-intel-opencl-code-builder&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;As far as I know it lists all of them.&lt;/P&gt;

&lt;P&gt;I suspect what you're looking for is SPIR-V. &amp;nbsp;It's an improvement on SPIR but that is more of an answer to look forward to in the future than something you could switch to today.&lt;/P&gt;</description>
      <pubDate>Wed, 02 Nov 2016 07:47:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/OpenCL-for-CPU/How-to-protect-OpenCL-kernel-code/m-p/1070965#M4436</guid>
      <dc:creator>Jeffrey_M_Intel1</dc:creator>
      <dc:date>2016-11-02T07:47:47Z</dc:date>
    </item>
  </channel>
</rss>

