<?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 icx: data corruption at -O2 in Intel® oneAPI DPC++/C++ Compiler</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/icx-data-corruption-at-O2/m-p/1597842#M3738</link>
    <description>&lt;P&gt;I am building main.c (attached) with icx&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Intel(R) oneAPI DPC++/C++ Compiler 2023.2.0 (2023.2.0.20230622)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The expected output of the program is "0 1 2 3 4 5 6 7." However, when compiled with -O2, the application returns incorrect data. We suspect that icx is reversing the loop at L22-L23 and this results in data corruption.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;[cmelone@shepard-login-0-1 bug]$ icx -O1 main.c
[cmelone@shepard-login-0-1 bug]$ ./a.out
0 1 2 3 4 5 6 7 
[cmelone@shepard-login-0-1 bug]$ icx -O2 main.c
[cmelone@shepard-login-0-1 bug]$ ./a.out 
0 1 2 3 0 2 0 2.125&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am not able to reproduce this with icc.&lt;/P&gt;</description>
    <pubDate>Wed, 15 May 2024 07:11:32 GMT</pubDate>
    <dc:creator>cmelone</dc:creator>
    <dc:date>2024-05-15T07:11:32Z</dc:date>
    <item>
      <title>icx: data corruption at -O2</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/icx-data-corruption-at-O2/m-p/1597842#M3738</link>
      <description>&lt;P&gt;I am building main.c (attached) with icx&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Intel(R) oneAPI DPC++/C++ Compiler 2023.2.0 (2023.2.0.20230622)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The expected output of the program is "0 1 2 3 4 5 6 7." However, when compiled with -O2, the application returns incorrect data. We suspect that icx is reversing the loop at L22-L23 and this results in data corruption.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;[cmelone@shepard-login-0-1 bug]$ icx -O1 main.c
[cmelone@shepard-login-0-1 bug]$ ./a.out
0 1 2 3 4 5 6 7 
[cmelone@shepard-login-0-1 bug]$ icx -O2 main.c
[cmelone@shepard-login-0-1 bug]$ ./a.out 
0 1 2 3 0 2 0 2.125&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am not able to reproduce this with icc.&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2024 07:11:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/icx-data-corruption-at-O2/m-p/1597842#M3738</guid>
      <dc:creator>cmelone</dc:creator>
      <dc:date>2024-05-15T07:11:32Z</dc:date>
    </item>
    <item>
      <title>Re: icx: data corruption at -O2</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/icx-data-corruption-at-O2/m-p/1598007#M3743</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Happens on oneAPI DPC++/C++ Compiler 2024.2 too, escalated the issue to our engineering team.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 15 May 2024 19:51:51 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/icx-data-corruption-at-O2/m-p/1598007#M3743</guid>
      <dc:creator>Alex_Y_Intel</dc:creator>
      <dc:date>2024-05-15T19:51:51Z</dc:date>
    </item>
    <item>
      <title>Re:icx: data corruption at -O2</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/icx-data-corruption-at-O2/m-p/1598103#M3750</link>
      <description>&lt;P&gt;I reported the issue to our internal team. Will let you know when the issue is fixed.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Chen&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 16 May 2024 03:10:47 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/icx-data-corruption-at-O2/m-p/1598103#M3750</guid>
      <dc:creator>cw_intel</dc:creator>
      <dc:date>2024-05-16T03:10:47Z</dc:date>
    </item>
    <item>
      <title>Re:icx: data corruption at -O2</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/icx-data-corruption-at-O2/m-p/1601391#M3790</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;​&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: -apple-system, BlinkMacSystemFont, &amp;quot;Segoe UI&amp;quot;, Roboto, Oxygen, Ubuntu, &amp;quot;Fira Sans&amp;quot;, &amp;quot;Droid Sans&amp;quot;, &amp;quot;Helvetica Neue&amp;quot;, sans-serif; font-size: 14px;"&gt;This is not a bug. The test case is violating ansi-alias semantics by casting (double * a) into (float *) and &lt;/SPAN&gt;hence has undefined behavior. To get the same results as -O1, you can compile the code with option '-fno-strict-aliasing'. &lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 28 May 2024 06:11:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-DPC-C-Compiler/icx-data-corruption-at-O2/m-p/1601391#M3790</guid>
      <dc:creator>cw_intel</dc:creator>
      <dc:date>2024-05-28T06:11:12Z</dc:date>
    </item>
  </channel>
</rss>

