<?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 enqueueReadBufferRect() doesn't work in Xeon PHI in OpenCL* for CPU</title>
    <link>https://community.intel.com/t5/OpenCL-for-CPU/enqueueReadBufferRect-doesn-t-work-in-Xeon-PHI/m-p/1006540#M2950</link>
    <description>&lt;P&gt;Hi guys,&lt;/P&gt;

&lt;P&gt;Have you ever tried the enqueueReadBufferRect() call for the Xeon PHI? It seems that there is a bug in the implementation for this function.&lt;/P&gt;

&lt;P&gt;This call copies a region of data from the device to the host. You can s&lt;span class="lia-inline-image-display-wrapper" image-alt="para_intel.png"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/7285i8557EB1F5A43D1C9/image-size/large?v=v2&amp;amp;px=999&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="para_intel.png" alt="para_intel.png" /&gt;&lt;/span&gt;et the row pitch and the slide pitch for device side and host side. If you try to copy data from the device to the host, there are some positions in the host pointer that are not updated. The picture at right shows an example of this wrong behaviour implemented in the attached source code. The zeros in red are wrong data, their data should be twos.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;It doesn't happen in Nvidia GPUs, neither ATI GPUs or INTEL CPUs. This incorrect behaviour only occurs for the Xeon PHI. Please, Somebody had the same problem?&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Thank you so much,&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Moisés Viñas&lt;/P&gt;</description>
    <pubDate>Wed, 11 Feb 2015 15:05:49 GMT</pubDate>
    <dc:creator>moises_v_</dc:creator>
    <dc:date>2015-02-11T15:05:49Z</dc:date>
    <item>
      <title>enqueueReadBufferRect() doesn't work in Xeon PHI</title>
      <link>https://community.intel.com/t5/OpenCL-for-CPU/enqueueReadBufferRect-doesn-t-work-in-Xeon-PHI/m-p/1006540#M2950</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;

&lt;P&gt;Have you ever tried the enqueueReadBufferRect() call for the Xeon PHI? It seems that there is a bug in the implementation for this function.&lt;/P&gt;

&lt;P&gt;This call copies a region of data from the device to the host. You can s&lt;span class="lia-inline-image-display-wrapper" image-alt="para_intel.png"&gt;&lt;img src="https://community.intel.com/t5/image/serverpage/image-id/7285i8557EB1F5A43D1C9/image-size/large?v=v2&amp;amp;px=999&amp;amp;whitelist-exif-data=Orientation%2CResolution%2COriginalDefaultFinalSize%2CCopyright" role="button" title="para_intel.png" alt="para_intel.png" /&gt;&lt;/span&gt;et the row pitch and the slide pitch for device side and host side. If you try to copy data from the device to the host, there are some positions in the host pointer that are not updated. The picture at right shows an example of this wrong behaviour implemented in the attached source code. The zeros in red are wrong data, their data should be twos.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;It doesn't happen in Nvidia GPUs, neither ATI GPUs or INTEL CPUs. This incorrect behaviour only occurs for the Xeon PHI. Please, Somebody had the same problem?&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Thank you so much,&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;Moisés Viñas&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2015 15:05:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/OpenCL-for-CPU/enqueueReadBufferRect-doesn-t-work-in-Xeon-PHI/m-p/1006540#M2950</guid>
      <dc:creator>moises_v_</dc:creator>
      <dc:date>2015-02-11T15:05:49Z</dc:date>
    </item>
    <item>
      <title>Hi Moisés,</title>
      <link>https://community.intel.com/t5/OpenCL-for-CPU/enqueueReadBufferRect-doesn-t-work-in-Xeon-PHI/m-p/1006541#M2951</link>
      <description>Hi Moisés,

I will try to reproduce this issue. I will let you know the result.

Thanks,
Yuri</description>
      <pubDate>Tue, 17 Feb 2015 13:21:20 GMT</pubDate>
      <guid>https://community.intel.com/t5/OpenCL-for-CPU/enqueueReadBufferRect-doesn-t-work-in-Xeon-PHI/m-p/1006541#M2951</guid>
      <dc:creator>Yuri_K_Intel</dc:creator>
      <dc:date>2015-02-17T13:21:20Z</dc:date>
    </item>
  </channel>
</rss>

