<?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>tema Re: Compilation of Fortran Code in VS 2022 en Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739572#M178446</link>
    <description>&lt;P&gt;Thank you very much!!!&lt;/P&gt;&lt;P&gt;Disabling optimizations works! Now it gives me the same results.&lt;/P&gt;&lt;P&gt;But why did that work? What exactly is the compiler doing differently now?&lt;/P&gt;</description>
    <pubDate>Wed, 04 Mar 2026 19:26:53 GMT</pubDate>
    <dc:creator>Jaensch</dc:creator>
    <dc:date>2026-03-04T19:26:53Z</dc:date>
    <item>
      <title>Compilation of Fortran Code in VS 2022</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739537#M178440</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;At the moment I am trying to compile an older .F file for a combustion model in GT Power.&lt;BR /&gt;In the next step, I want to make some changes to the older .F combustion model. But first, I want to find a solution to compile the Fortran code.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Using the procedure from the UserCode.pdf and Visual Studio, I can build a .dll file.&lt;/P&gt;&lt;P&gt;But if I use the same GT model for the older .dll and for the new .dll, I do not get the same results.&lt;BR /&gt;In both cases, however, I used the same .F code and the same GT model.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So I think the only difference is the compiler. Because now I use Visual Studio 2022, and the older .dll it was 2015. But should the compiler affect the results, or did I overlook something?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here are the Setups:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My old setup in GT 2024:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;GT version: v2024&lt;/LI&gt;&lt;LI&gt;Fortran code&lt;/LI&gt;&lt;LI&gt;UserCodeReference folder used: %GTIHOME%\v2020\usercode\Fortran\UserCodeReference&lt;/LI&gt;&lt;LI&gt;Microsoft Visual Studio: version 2015 à Intel Parallel Studio XE 2017&lt;/LI&gt;&lt;LI&gt;Binary file: .dll generated from the above&lt;/LI&gt;&lt;LI&gt;Results: stored after running the GT v2024 model with the .dll&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My current setup:&lt;/P&gt;&lt;UL class="lia-list-style-type-square"&gt;&lt;LI&gt;GT version: v2024&lt;/LI&gt;&lt;LI&gt;Fortan code (unchanged)&lt;/LI&gt;&lt;LI&gt;UserCodeReference folder used: %GTIHOME%\v2020\usercode\Fortran\UserCodeReference&lt;/LI&gt;&lt;LI&gt;Microsoft Visual Studio: version 2022 à Intel® Fortran Compiler 2025.3.2 [Intel(R) 64]&lt;/LI&gt;&lt;LI&gt;Binary file: .dll generated from the above&lt;/LI&gt;&lt;LI&gt;Results: stored after running the GT v2024 model with the .dll&lt;BR /&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I know it is difficult to present a solution with so little information, but maybe anybody have a few ideas about what it could be caused by.&lt;/P&gt;Thanks for any helpt!&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Jaensch&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2026 13:49:09 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739537#M178440</guid>
      <dc:creator>Jaensch</dc:creator>
      <dc:date>2026-03-04T13:49:09Z</dc:date>
    </item>
    <item>
      <title>Re: Compilation of Fortran Code in VS 2022</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739550#M178443</link>
      <description>&lt;P&gt;This may be a floating point issue.&lt;/P&gt;&lt;P&gt;First try disabling optimizations.&lt;/P&gt;&lt;P&gt;That failing, in the project properties, try setting the&lt;/P&gt;&lt;P&gt;Properties | Fortran | Code Generation | Intel Processor-Specific Optimization | (pull down) ...&lt;/P&gt;&lt;P&gt;and select older ISA (QxSSE3, or QxAVX).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jim Dempsey&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2026 16:20:13 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739550#M178443</guid>
      <dc:creator>jimdempseyatthecove</dc:creator>
      <dc:date>2026-03-04T16:20:13Z</dc:date>
    </item>
    <item>
      <title>Re: Compilation of Fortran Code in VS 2022</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739572#M178446</link>
      <description>&lt;P&gt;Thank you very much!!!&lt;/P&gt;&lt;P&gt;Disabling optimizations works! Now it gives me the same results.&lt;/P&gt;&lt;P&gt;But why did that work? What exactly is the compiler doing differently now?&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2026 19:26:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739572#M178446</guid>
      <dc:creator>Jaensch</dc:creator>
      <dc:date>2026-03-04T19:26:53Z</dc:date>
    </item>
    <item>
      <title>Re: Compilation of Fortran Code in VS 2022</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739585#M178447</link>
      <description>&lt;P&gt;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/474970"&gt;@Jaensch&lt;/a&gt;, from your description, it appears that the original code was compiled with optimizations off. Whoever did that was a defensive programmer. When performing optimizations, the compiler writes object code that it thinks will improve the speed of execution in comparison to the non-optimized object code. As you have encountered, there may be differences in the results that are produced by optimized and non-optimized code. With any program, particularly larger codebases, it may be prudent to initially compile with all optimizations turned off. In my experience, this seems to be a reasonable and robust approach to take.&lt;/P&gt;</description>
      <pubDate>Wed, 04 Mar 2026 21:21:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739585#M178447</guid>
      <dc:creator>witwald</dc:creator>
      <dc:date>2026-03-04T21:21:05Z</dc:date>
    </item>
    <item>
      <title>Re: Compilation of Fortran Code in VS 2022</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739702#M178451</link>
      <description>&lt;P&gt;Thank you for the explanation!&lt;/P&gt;</description>
      <pubDate>Thu, 05 Mar 2026 08:56:06 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Compilation-of-Fortran-Code-in-VS-2022/m-p/1739702#M178451</guid>
      <dc:creator>Jaensch</dc:creator>
      <dc:date>2026-03-05T08:56:06Z</dc:date>
    </item>
  </channel>
</rss>

