<?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: /Qvec-report interferes with Call Graph Instrumentation in Analyzers</title>
    <link>https://community.intel.com/t5/Analyzers/Qvec-report-interferes-with-Call-Graph-Instrumentation/m-p/915166#M6000</link>
    <description>&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;Dear Nafis,&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;The switch /Qvec-report3 forces the build of some extra debugging information to enable reporting variable identifiers indetailed data dependence reports. I was not aware this interfered with call graph construction (you may want to report this through premier). Switch /Qvec-report2 (and lower) does not require this information, and still gives you information on the success and failure of vectorizing your code. Hope this helps for now at least.&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;Aart Bik&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;A href="http://www.aartbik.com/"&gt;http://www.aartbik.com/&lt;/A&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;P&gt;&lt;/P&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 28 Jul 2006 14:20:12 GMT</pubDate>
    <dc:creator>Intel_C_Intel</dc:creator>
    <dc:date>2006-07-28T14:20:12Z</dc:date>
    <item>
      <title>/Qvec-report interferes with Call Graph Instrumentation</title>
      <link>https://community.intel.com/t5/Analyzers/Qvec-report-interferes-with-Call-Graph-Instrumentation/m-p/915165#M5999</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;After spending the last 3 hours trying to figure out why the Call Graph wasn't showing the function in which 99% of program execution is spent, I finally got it to work by simply removing the /Qvec-report3 compiler switch. I have verified that this switch interferes with instrumentation on two different machines using Visual Studio .NET 2003. Perhaps only those functions in which vectorization occurs are affected -- I'm not sure. &lt;/P&gt;
&lt;P&gt;~Nafis&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2006 13:17:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Qvec-report-interferes-with-Call-Graph-Instrumentation/m-p/915165#M5999</guid>
      <dc:creator>nupshur</dc:creator>
      <dc:date>2006-07-28T13:17:30Z</dc:date>
    </item>
    <item>
      <title>Re: /Qvec-report interferes with Call Graph Instrumentation</title>
      <link>https://community.intel.com/t5/Analyzers/Qvec-report-interferes-with-Call-Graph-Instrumentation/m-p/915166#M6000</link>
      <description>&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;Dear Nafis,&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;The switch /Qvec-report3 forces the build of some extra debugging information to enable reporting variable identifiers indetailed data dependence reports. I was not aware this interfered with call graph construction (you may want to report this through premier). Switch /Qvec-report2 (and lower) does not require this information, and still gives you information on the success and failure of vectorizing your code. Hope this helps for now at least.&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;Aart Bik&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;A href="http://www.aartbik.com/"&gt;http://www.aartbik.com/&lt;/A&gt;&lt;/P&gt;
&lt;P class="MsoNormal" style="MARGIN: 0cm 0cm 0pt"&gt;&lt;P&gt;&lt;/P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2006 14:20:12 GMT</pubDate>
      <guid>https://community.intel.com/t5/Analyzers/Qvec-report-interferes-with-Call-Graph-Instrumentation/m-p/915166#M6000</guid>
      <dc:creator>Intel_C_Intel</dc:creator>
      <dc:date>2006-07-28T14:20:12Z</dc:date>
    </item>
  </channel>
</rss>

