<?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 ivf11.1.072/73 + openmp in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749860#M6629</link>
    <description>&lt;P&gt;Thank you for your help, Patrick.&lt;/P&gt;</description>
    <pubDate>Thu, 21 Oct 2010 13:07:49 GMT</pubDate>
    <dc:creator>yeg001</dc:creator>
    <dc:date>2010-10-21T13:07:49Z</dc:date>
    <item>
      <title>ivf11.1.072/73 + openmp</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749856#M6625</link>
      <description>Hi, every one. Iencountered a defect when i used ivf11.1.072/73for linux. And my firend tested it ina someedition ofivf for windows. And he also find it. &lt;BR /&gt;&lt;BR /&gt;I compile the file like this,&lt;BR /&gt;&lt;STRONG&gt;ifort 1dshggl.for -openmp&lt;BR /&gt;&lt;/STRONG&gt;and the outputarrayew1 is differntfrom ew2. &lt;BR /&gt;&lt;BR /&gt;with out "-openmp", or other versions of ivf, such as 11.1.038, it is fine.</description>
      <pubDate>Tue, 19 Oct 2010 16:36:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749856#M6625</guid>
      <dc:creator>yeg001</dc:creator>
      <dc:date>2010-10-19T16:36:35Z</dc:date>
    </item>
    <item>
      <title>ivf11.1.072/73 + openmp</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749857#M6626</link>
      <description>It appears to be an -O2 or higher optimisation bug. I see correct results at -O0/-O1. Let me investigate, and I'll get back to you.&lt;BR /&gt;&lt;BR /&gt;Patrick Kennedy&lt;BR /&gt;Intel Developer Support</description>
      <pubDate>Tue, 19 Oct 2010 21:49:41 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749857#M6626</guid>
      <dc:creator>pbkenned1</dc:creator>
      <dc:date>2010-10-19T21:49:41Z</dc:date>
    </item>
    <item>
      <title>ivf11.1.072/73 + openmp</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749858#M6627</link>
      <description>Thank you for your reply. I had tried to simplify the code, but failed. I hope it can help intel to improve openmp and fix the defect in next update.</description>
      <pubDate>Wed, 20 Oct 2010 05:10:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749858#M6627</guid>
      <dc:creator>yeg001</dc:creator>
      <dc:date>2010-10-20T05:10:39Z</dc:date>
    </item>
    <item>
      <title>ivf11.1.072/73 + openmp</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749859#M6628</link>
      <description>This has been reported to compiler engineering as defect #DPD200161914. I'll pass along updates I receive from the developers. The bug exists in Linux compiler 11.1.069 or later, and is present in v12.0 as well. The last known good Linux compiler is 11.1.064.&lt;BR /&gt;&lt;BR /&gt;Patrick</description>
      <pubDate>Wed, 20 Oct 2010 15:25:52 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749859#M6628</guid>
      <dc:creator>pbkenned1</dc:creator>
      <dc:date>2010-10-20T15:25:52Z</dc:date>
    </item>
    <item>
      <title>ivf11.1.072/73 + openmp</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749860#M6629</link>
      <description>&lt;P&gt;Thank you for your help, Patrick.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Oct 2010 13:07:49 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749860#M6629</guid>
      <dc:creator>yeg001</dc:creator>
      <dc:date>2010-10-21T13:07:49Z</dc:date>
    </item>
    <item>
      <title>ivf11.1.072/73 + openmp</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749861#M6630</link>
      <description>This issueshould be fixed in Intel Fortran Compiler XE Update #2 (the V12.0 compiler),which we plan to release shortly. I'll update this thread with the package identifiers once the packages are posted in the download center.&lt;BR /&gt;&lt;BR /&gt;Patrick Kennedy</description>
      <pubDate>Mon, 17 Jan 2011 19:06:21 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749861#M6630</guid>
      <dc:creator>pbkenned1</dc:creator>
      <dc:date>2011-01-17T19:06:21Z</dc:date>
    </item>
    <item>
      <title>ivf11.1.072/73 + openmp</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749862#M6631</link>
      <description>This issue is resolved in ifort XE update #2. The packages containing the fixes are:&lt;BR /&gt;&lt;BR /&gt;&lt;P&gt;l_fcompxe_2011.2.137 (Linux*)&lt;/P&gt;&lt;P&gt;m_fcompxe_2011.2.142 (Mac OS X*)&lt;/P&gt;&lt;P&gt;w_fcompxe_2011.2.154 (Windows*)&lt;BR /&gt;&lt;BR /&gt;Patrick Kennedy&lt;/P&gt;</description>
      <pubDate>Wed, 02 Feb 2011 19:45:48 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/ivf11-1-072-73-openmp/m-p/749862#M6631</guid>
      <dc:creator>pbkenned1</dc:creator>
      <dc:date>2011-02-02T19:45:48Z</dc:date>
    </item>
  </channel>
</rss>

