<?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 Re:Vtune func@ problems +IFORT + Visual studio 2019 in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1363903#M21922</link>
    <description>&lt;P&gt;I'm going to close this thread for support as a duplicate of &lt;A href="https://community.intel.com/t5/Intel-Fortran-Compiler/Vtune-problems-Ifort-vs2019/m-p/1350470" target="_blank"&gt;https://community.intel.com/t5/Intel-Fortran-Compiler/Vtune-problems-Ifort-vs2019/m-p/1350470&lt;/A&gt;.  VTune is not related to the actual problem, it is simply a way to see the problem.&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Fri, 25 Feb 2022 20:06:39 GMT</pubDate>
    <dc:creator>James_T_Intel</dc:creator>
    <dc:date>2022-02-25T20:06:39Z</dc:date>
    <item>
      <title>Vtune func@ problems +IFORT + Visual studio 2019</title>
      <link>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1350274#M21756</link>
      <description>&lt;P&gt;Hello.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;There is a problem with Vtune + ifort 2022 + vs2019.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;&lt;FONT color="#C81326"&gt;Can you please tell me how to make it so that instead of references like func@0x140051b90 &lt;/FONT&gt;&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;&lt;FONT color="#C81326"&gt;to output function names from source Fortran program?&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;If I disable /O0 optimization, then function names are displayed correctly.&lt;BR /&gt;However, if I use /O3, I get addresses instead of names.&lt;/P&gt;
&lt;P&gt;The compilation is carried out with the parameters&lt;/P&gt;
&lt;P&gt;/&lt;FONT color="#1E2EB8"&gt;nologo /debug:full /O3 /Qaxcoffeelake /Qxcoffeelake /reentrancy:none /arch:AVX /Qoffload:none /tune:coffeelake /Qopenmp-offload- /Qopenmp-stubs interfaces /Qopt-report:5 /fpe:0 /module: "x64\Release\\" /object: "x64\Release\\" /Fd "x64\Release\vc160. pdb" /traceback /libs:static /threads /Qmkl:sequential /c&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;Linking with parameters&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#1E2EB8"&gt;/OUT: "x64\Release\neumann_1d_msu.exe" /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE: "x64\Release\neumann_1d_msu.exe.intermediate.manifest" /MANIFESTUAC: "level='asInvoker' uiAccess='false'" /DEBUG /PDB: "d:\Disk\Parallel\fortran\2d_Extra_Laguerre_ALL\2d_Extra_Laguerre8\x64\Release\neumann_1d_msu. pdb" /MAP /MAPINFO:EXPORTS /SUBSYSTEM:CONSOLE /STACK:2000000000,2000000000 /IMPLIB: "d:\Disk\Parallel\fortran\2d_Extra_Laguerre_ALL\2d_Extra_Laguerre8\x64\Release\neumann_1d_msu.lib"&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For linux system I have no problem with this.&lt;BR /&gt;&lt;BR /&gt;Thank you.&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;</description>
      <pubDate>Tue, 11 Jan 2022 03:22:32 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1350274#M21756</guid>
      <dc:creator>Andrew_</dc:creator>
      <dc:date>2022-01-11T03:22:32Z</dc:date>
    </item>
    <item>
      <title>Re: Vtune func@ problems +IFORT + Visual studio 2019</title>
      <link>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1350321#M21759</link>
      <description>&lt;P&gt;&amp;nbsp;VTune reads information about function names from .pdb files. Are there any warning messages about symbol file of this module in VTune finalization output/log? Can you see function names for this module under VS debugger?&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;Can your share a reproducer: small VTune result + executable module (this program or any other "hello world" app with such issue) + its .pdb file?&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jan 2022 07:34:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1350321#M21759</guid>
      <dc:creator>Denis_M_Intel</dc:creator>
      <dc:date>2022-01-11T07:34:39Z</dc:date>
    </item>
    <item>
      <title>Re: Vtune func@ problems +IFORT + Visual studio 2019</title>
      <link>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1350334#M21760</link>
      <description>&lt;P&gt;I have attached a visual studio 2019 project with a simple program and Vtune result.&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jan 2022 08:08:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1350334#M21760</guid>
      <dc:creator>Andrew_</dc:creator>
      <dc:date>2022-01-11T08:08:02Z</dc:date>
    </item>
    <item>
      <title>Re: Vtune func@ problems +IFORT + Visual studio 2019</title>
      <link>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1350459#M21765</link>
      <description>&lt;P&gt;Thank you for providing the reproducer. The attached .exe file doesn't have information about its .pdb in the&amp;nbsp;&lt;SPAN&gt;IMAGE_DEBUG_TYPE_CODEVIEW debug directory. As a result, VTune doesn't try to find the .pdb. Help is needed from the Compiler team to understand why there&amp;nbsp;is no reference to .pdb.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 11 Jan 2022 14:50:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1350459#M21765</guid>
      <dc:creator>Denis_M_Intel</dc:creator>
      <dc:date>2022-01-11T14:50:55Z</dc:date>
    </item>
    <item>
      <title>Re:Vtune func@ problems +IFORT + Visual studio 2019</title>
      <link>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1360504#M21847</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We are working on this internally, will get back to you with the solution. Thank you for your patience.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Raeesa&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 15 Feb 2022 11:58:41 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1360504#M21847</guid>
      <dc:creator>RaeesaM_Intel</dc:creator>
      <dc:date>2022-02-15T11:58:41Z</dc:date>
    </item>
    <item>
      <title>Re:Vtune func@ problems +IFORT + Visual studio 2019</title>
      <link>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1363903#M21922</link>
      <description>&lt;P&gt;I'm going to close this thread for support as a duplicate of &lt;A href="https://community.intel.com/t5/Intel-Fortran-Compiler/Vtune-problems-Ifort-vs2019/m-p/1350470" target="_blank"&gt;https://community.intel.com/t5/Intel-Fortran-Compiler/Vtune-problems-Ifort-vs2019/m-p/1350470&lt;/A&gt;.  VTune is not related to the actual problem, it is simply a way to see the problem.&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Feb 2022 20:06:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Vtune-func-problems-IFORT-Visual-studio-2019/m-p/1363903#M21922</guid>
      <dc:creator>James_T_Intel</dc:creator>
      <dc:date>2022-02-25T20:06:39Z</dc:date>
    </item>
  </channel>
</rss>

