@ Stephen T
What kind of analysis type did you use? Hotspots analysis will collect stack info automatically if you had debug info built.
If you use advanced-hotspots, please add option "-knob collection-detail=stack-sampling" which will collect call stack information,
BTW, VTune(TM) Amplifier XE 2015 Update 1 is ready for now.
@ Stephen T
I saw you had another thread 534715, which attached hotspots result r021hs.
In that report, there was more IDLE time (1.353s) than serial time (0.651s), and top 1-N hot functions were dropped in ntdll.dll, MSVCR100.dll, and kernel32.dll. Hot function "std::getline<...>" in your module Test.exe only took 6.002ms with [No call stack information]. Actually, I doubt that your function was called by ntdll.dll which has no symbol info, this caused no stack info to be displayed.
You can try to build test case which spends more CPU time, and make a caller in your code which call your hot function(s) - thus, caller will not be in ntdll.dll, to verify this issue. Hope it helps.
>>> But it seems that there is a problem for one of the subroutine: the displayed time is written for a comment line ?!? or for a line with nothing (see figure in attachment)...I can't read assembly code.>>>
It seems that <Block 19> is a loop which is copying values from R15 register to different GP registers. I cannot see call instruction and I cannot see do loop construct in the source code on the left pane.Put it simply left pane does not correspond to right pane.