<?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 Too imprecise native_sin/native_cos implementation. in OpenCL* for CPU</title>
    <link>https://community.intel.com/t5/OpenCL-for-CPU/Too-imprecise-native-sin-native-cos-implementation/m-p/972941#M2409</link>
    <description>&lt;P&gt;Running my OpenCL app on Intel GPUs I encountered precision issue. Results were too imprecise and often failed to pass validation vs CPU-based (or AMD/nVidia GPU based) ones.&lt;/P&gt;
&lt;P&gt;Considerable improvement was only when I refused from native_cos/native_sin in oclFFT &amp;nbsp;(Apple's FFT release for OpenCL) and in other parts of app code.&lt;/P&gt;
&lt;P&gt;I have no such issues with same OpenCL code on GPUs from other vendors (both AMD and nVidia).&lt;/P&gt;
&lt;P&gt;Please consider some improvements for native trigonometric function presion in future SDK/hardware releases. Too low precision makes them just un-useful no matter how speedy they are. Make precision at least in line with other vendors.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 02 Nov 2013 09:46:37 GMT</pubDate>
    <dc:creator>Raistmer</dc:creator>
    <dc:date>2013-11-02T09:46:37Z</dc:date>
    <item>
      <title>Too imprecise native_sin/native_cos implementation.</title>
      <link>https://community.intel.com/t5/OpenCL-for-CPU/Too-imprecise-native-sin-native-cos-implementation/m-p/972941#M2409</link>
      <description>&lt;P&gt;Running my OpenCL app on Intel GPUs I encountered precision issue. Results were too imprecise and often failed to pass validation vs CPU-based (or AMD/nVidia GPU based) ones.&lt;/P&gt;
&lt;P&gt;Considerable improvement was only when I refused from native_cos/native_sin in oclFFT &amp;nbsp;(Apple's FFT release for OpenCL) and in other parts of app code.&lt;/P&gt;
&lt;P&gt;I have no such issues with same OpenCL code on GPUs from other vendors (both AMD and nVidia).&lt;/P&gt;
&lt;P&gt;Please consider some improvements for native trigonometric function presion in future SDK/hardware releases. Too low precision makes them just un-useful no matter how speedy they are. Make precision at least in line with other vendors.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 02 Nov 2013 09:46:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/OpenCL-for-CPU/Too-imprecise-native-sin-native-cos-implementation/m-p/972941#M2409</guid>
      <dc:creator>Raistmer</dc:creator>
      <dc:date>2013-11-02T09:46:37Z</dc:date>
    </item>
    <item>
      <title>Native functions should be</title>
      <link>https://community.intel.com/t5/OpenCL-for-CPU/Too-imprecise-native-sin-native-cos-implementation/m-p/972942#M2410</link>
      <description>&lt;P&gt;Native functions should be faster but not necessarily precise. I am not sure how much difference is acceptable. Are you seeing precision issues with native_sin and native_cos only? Thanks for the feedback.&lt;/P&gt;
&lt;P&gt;Raghu&lt;/P&gt;</description>
      <pubDate>Tue, 05 Nov 2013 00:46:24 GMT</pubDate>
      <guid>https://community.intel.com/t5/OpenCL-for-CPU/Too-imprecise-native-sin-native-cos-implementation/m-p/972942#M2410</guid>
      <dc:creator>Raghupathi_M_Intel</dc:creator>
      <dc:date>2013-11-05T00:46:24Z</dc:date>
    </item>
  </channel>
</rss>

