Analyzers
Community support for Analyzers (Intel VTune™ Profiler, Intel Advisor, Intel Inspector)
4892 Discussions

/Qvec-report interferes with Call Graph Instrumentation

nupshur
Beginner
‎07-28-2006 06:17 AM
190 Views

Hi,

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.

~Nafis

0 Kudos

Link Copied

1 Reply
Intel_C_Intel
Employee
‎07-28-2006 07:20 AM
190 Views

Dear Nafis,

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.

Aart Bik

http://www.aartbik.com/

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.