|
From: Dallman, J. <joh...@si...> - 2014-02-13 09:18:13
|
Philippe Waroquiers <phi...@sk...> wrote: > Starting callgrind with default options, and then using > kcachegrind on the resulting callgrind.out file, kcachegrind > shows the nr of calls to the functions. I'm trying to avoid using kcachegrind, because I need to automate this process. We have tens of thousands of test cases we'll want to feed through this and requiring human interaction is thus bad. Josef Weidendorfer [mailto:Jos...@gm...] wrote: > Yes. Call counts are special. Aha. > --tree=caller shows the callers of each function, with the call > count in parenthesis. Yup, and that output looks a lot easier to parse than the full callgrind output. I have something odd in the output, though: I have a lot of calls to functions with names that I recognise, but which have a '2 appended to their names. These don't exist in the source: any idea what they signify? 8,658,501 < ???:read__list'2 (5826x) [kid.out] 128,976,260 < ???:read_sub_list'2 (158404x) [kid.out] 2,107 < ???:relax'2 (43x) [kid.out] 2,416,508 < ???:REL_gen_external'2 (437x) [kid.out] > Hmm. It should be easy to show the summed up call count for each > function also without callers/callee display. That would be nice if it could be added easily. thanks, everyone, -- John Dallman ----------------- Siemens Industry Software Limited is a limited company registered in England and Wales. Registered number: 3476850. Registered office: Faraday House, Sir William Siemens Square, Frimley, Surrey, GU16 8QD. |