[Enhancement] Add VTune Amplifier XE format

[GoogleCodeExporter]

[Don't know how to change the tracking type from "Defect" to "Enhancement."]

The attached patch against gprof2dot.py 1.0 rev. 2012-11-25 adds the gprof-cc 
report format produced by Intel VTune Amplifier XE 2013 as format 'axe'.  Only 
the Windows version has been tested.

The total time of functions as reported by AXE is used.  OTOH, the weighting of 
calls is faked from total time (with a warning message) since the call counts 
are not available.

This cumulative patch includes the earlier patch, "Calculate true total time 
with perf" (Issue 77).

Original issue reported on code.google.com by dfla...@nist.gov on 4 Mar 2013 at 7:28

Attachments:

• gprof2dot.py-20121125-DWF1.2.patch

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

1.2 DWF --> 1.2.1 DWF, added missing help text for axe format.

Original comment by dfla...@nist.gov on 4 Mar 2013 at 7:52

Attachments:

• gprof2dot.py-20121125-DWF1.2.1.patch

[GoogleCodeExporter]

Patch applied, minus the earlier patch for issue 77.

Thanks!

It would be nice to eventually refactor AXE and GProf parser so they share some 
code. But I don't think that's reason to withhold applying this patch as is any 
longer

Original comment by Jose.R.F...@gmail.com on 8 Apr 2013 at 4:55

• Changed state: Fixed
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

I am getting "error: unexpected end of file" using the axe format:

~/bin/gprof2dot.py  -f axe hs_prof.txt
warning: for axe format, edge weights are unreliable estimates derived from
function total times.
warning: unrecognized call graph entry (1): '------  ----------------  
-------------  -----------------  
------------------------------------------------------------------------------- 
 ------'
error: unexpected end of file

see the attached input file.

Original comment by threed...@gmail.com on 2 Jul 2013 at 11:46

Attachments:

• hs_prof.txt

[GoogleCodeExporter]

Fixed now.

Original comment by Jose.R.F...@gmail.com on 3 Jul 2013 at 6:57

[GoogleCodeExporter]

This issue was closed by revision 657414322137.

Original comment by Jose.R.F...@gmail.com on 3 Jul 2013 at 6:57

[GoogleCodeExporter]

This issue was closed by revision 97c008248196.

Original comment by Jose.R.F...@gmail.com on 3 Jul 2013 at 7:15