<?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 PGO with slightly different source code than was used to genera in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/PGO-with-slightly-different-source-code-than-was-used-to/m-p/757920#M13407</link>
    <description>It might, if the number of "basic blocks" of code paths changed. If it didn't, the results could mislead the compiler into making optimization choices it shouldn't.&lt;BR /&gt;</description>
    <pubDate>Thu, 22 Sep 2011 20:34:30 GMT</pubDate>
    <dc:creator>Steven_L_Intel1</dc:creator>
    <dc:date>2011-09-22T20:34:30Z</dc:date>
    <item>
      <title>PGO with slightly different source code than was used to generate profiles</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/PGO-with-slightly-different-source-code-than-was-used-to/m-p/757917#M13404</link>
      <description>I'm in the final stages of testing a code, and I found typos in a couple of the error messages. Can I just do a recompile with PGO using the old profiles, or do I need to regenerate the profile data?&lt;SPAN style="font-family: Verdana, Arial, Helvetica, sans-serif;"&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/SPAN&gt;Thanks,&lt;DIV&gt;Greg&lt;/DIV&gt;</description>
      <pubDate>Thu, 22 Sep 2011 18:03:04 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/PGO-with-slightly-different-source-code-than-was-used-to/m-p/757917#M13404</guid>
      <dc:creator>gregfi04</dc:creator>
      <dc:date>2011-09-22T18:03:04Z</dc:date>
    </item>
    <item>
      <title>PGO with slightly different source code than was used to genera</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/PGO-with-slightly-different-source-code-than-was-used-to/m-p/757918#M13405</link>
      <description>If you just changed the text of a character string, you won't need to redo the profiles. But if you change the logic of the program, you would.</description>
      <pubDate>Thu, 22 Sep 2011 19:46:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/PGO-with-slightly-different-source-code-than-was-used-to/m-p/757918#M13405</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2011-09-22T19:46:15Z</dc:date>
    </item>
    <item>
      <title>PGO with slightly different source code than was used to genera</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/PGO-with-slightly-different-source-code-than-was-used-to/m-p/757919#M13406</link>
      <description>Great, thanks. If logic were changed, would the compiler be smart enough to detect a mismatch? If not, could it potentially cause problems?</description>
      <pubDate>Thu, 22 Sep 2011 20:01:35 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/PGO-with-slightly-different-source-code-than-was-used-to/m-p/757919#M13406</guid>
      <dc:creator>gregfi04</dc:creator>
      <dc:date>2011-09-22T20:01:35Z</dc:date>
    </item>
    <item>
      <title>PGO with slightly different source code than was used to genera</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/PGO-with-slightly-different-source-code-than-was-used-to/m-p/757920#M13407</link>
      <description>It might, if the number of "basic blocks" of code paths changed. If it didn't, the results could mislead the compiler into making optimization choices it shouldn't.&lt;BR /&gt;</description>
      <pubDate>Thu, 22 Sep 2011 20:34:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/PGO-with-slightly-different-source-code-than-was-used-to/m-p/757920#M13407</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2011-09-22T20:34:30Z</dc:date>
    </item>
  </channel>
</rss>

