Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
5255 Discussions

code analysis

satya_b_
Beginner
‎09-18-2013 05:01 AM
1,565 Views

Dear all,

           I want to debug code as well as analyse code through Vtune amplifier. I used following command

  ifort  -o  file.x -O3 -g  *.o . However , when I open the source code in Vtune amplifier, that particular subroutine is comming in the binary format. I have searched in  intel forums also, I could not get proper suggestions.  Could any one please suggest me, whether am I doing correct or wrong. I enclosed snapshots of my results.

Thank you.  

Preview file
247 KB
Preview file
287 KB
0 Kudos

Link Copied

2 Replies
TimP
Honored Contributor III
‎09-18-2013 06:23 AM
1,565 Views

In order for -g to take effect, it has to be set when making the .o as well as for the link step.

0 Kudos
Copy link
TimP
Honored Contributor III
‎09-18-2013 08:28 AM
1,565 Views

You showed your link step, which you have set up correctly to link against debug libraries.  This does not modify the .o files, which you apparently made without -g, so they don't have the debug symbols required to refer to source code.

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. 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.