We have been using vtune version 6.1/7-beta to carry out compile time analysis of applications. In this we remotely execute script which internally calls make. In the resultant output we target mcpcom and get function hotspots within this.
But when using vtl 1.0 for Linux when I execute the following
$>vtl activity mcpcomActivity -c sampling -o "-sample-buffer-size 5000" -app make -moi /opt/intel/compiler70/ia32/bin/mcpcom run $> vtl view -processes OR $> vtl view -modules
I dont see mcpcom but get to see /usr/bin/make. Is there a technique to drill down further into make to get information on mcpcom.
Based on the experiments conducted at my end: These are my results.
*cal = calibration hotsport indicates mcpcom information calibration is not done by using option -cal no
1. No cal :No duration : hotspot available 2. Cal allowed:No duration : hotspot available 3. Cal allowed:0 sec duration : VTL doesnt allow 4. No cal :0 sec duration : hot spot available 5. No cal :100 sec duration : hot spot available 6 Cal allowed:100 sec duration : no hotspot available