How to display call count in VTune™ Amplifier XE command line?

VTune™ Amplifier XE supports hardware PMU event-based sampling collection with call stack info & call count. 

For example:
# amplxe-cl -collect advanced-hotspots -knob collection-detail=stack-and-callcount -- ./primes.icc

If you want to see performance data on hot functions with call stack info, try this command line:

 
# amplxe-cl -report callstacks | more
amplxe: Using result path `/home/peter/problem_report/r002ah'
amplxe: Executing actions 100 % done                                           

Function                  Function Stack            Module              CPU Time
:Self
------------------------  ------------------------  ------------------  --------
-----
findPrimes                                          primes.icc          2.213
                          start_thread              libpthread-2.12.so  2.213
                          clone                     libc-2.12.so        0

                                                                         

Observe above result, hot function with CPU Time, call stack (caller) info were provided, but there was no call count info (column) – actually we enabled this when doing EBS sampling collection.

Alternatively, you can choose another report type named hotspots, it can display call count info. Do this:

# amplxe-cl -report hotspots | more
amplxe: Using result path `/home/peter/problem_report/r002ah'
amplxe: Executing actions 100 % done                                           

Function                             Module      CPU Time:Self  Estimated Call Count:Self
-----------------------------------  ----------  -------------  -------------------------
findPrimes                           primes.icc          2.213                          0
apic_timer_interrupt                 vmlinux             0.004                          0
[Unknown stack frame(s)]             [Unknown]           0.001                          0
_dl_lookup_symbol_x                  ld-2.12.so          0.001                          0
retint_careful                       vmlinux             0.001                          0
[Import thunk pthread_mutex_lock]    primes.icc              0                       6710
[Import thunk pthread_mutex_unlock]  primes.icc              0                       6710

You need to analyze two kinds of report file, and you may incorporate them to your result file?

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