Lines Matching full:calls
98 function calls that use a lot of time. *Note The Call Graph: Call
149 time seconds seconds calls Ts/call Ts/call name
160 you number-of-calls information for standard library functions such as
171 (except that the `calls' field for the functions will be blank), but
184 `-finstrument-functions' command line option which will insert calls to
222 directory_ at the time it exits. This means that if your program calls
473 spent in these functions, calls to/from them, etc., will all be
482 object file and identifies function calls in the binary machine
485 have been called, but never were. Calls to functions that were
487 if symbol table entries are present for them. Calls to dynamic
699 when its subroutine calls are included.
712 with no apparent time spent in them, and no apparent calls to them, are
723 time seconds seconds calls ms/call ms/call name
741 then by decreasing number of calls, then alphabetically by name. The
765 they are listed, sorted in decreasing order by the `calls' field.
785 `calls'
789 compiled with profiling enabled), the "calls" field is blank.
805 this field alphabetically after the "self seconds" and "calls"
872 such as `a' calls `b' calls `a'...
919 This is the total amount of time spent in the subroutine calls
928 separated by a `+'. The first number counts non-recursive calls,
929 and the second counts recursive calls.
977 amount of time spent within calls to `report' from `main'.
981 followed by the total number of non-recursive calls to `report'
991 of the functions it calls.
1032 total time spent in calls to `report' from `main'.
1035 Two numbers, the number of calls to `report' from `main' followed
1036 by the total number of non-recursive calls to `report'. This
1055 in the call graph. A cycle exists if a function calls another function
1056 that (directly or indirectly) calls (or appears to call) the original
1057 function. For example: if `a' calls `b', and `b' calls `a', then `a'
1063 `b' only calls `a' if it was not called from `a', `gprof' cannot
1109 for `main', which calls `a', and an entry for `c', with callers `a' and
1149 lines count only subroutines outside the cycle. Even though `a' calls
1150 `b', the time spent in those calls to `b' is not counted in `a''s
1152 when the time in those callscalls
1164 the cycle calls itself). This is a generalization of the usual split
1165 into non-recursive and recursive calls.
1206 13327 calls to `init_block'.
1212 time seconds seconds calls us/call us/call name
1233 note how `ct_init''s 13327 calls to `init_block' are broken down into
1234 one call from line 396, 3071 calls from line 384, 3730 calls from line
1235 385, and 6525 calls from 387.
1241 time seconds seconds calls name
1373 By contrast, the number-of-calls and basic-block figures are derived
1437 used 5 seconds in all, and 2/5 of the calls to `foo' came from `a',
1445 all the time spent in `foo' is in the calls from callers other than `a'.
1464 of calls to smaller ones. Beware however that this can introduce
1466 overhead to function calls. An alternative solution is to use a
1510 parent and as a child, with a `calls' field that lists the number
1511 of recursive calls. GNU `gprof' omits these lines and puts the
1512 number of recursive calls in the primary line.
1563 and then calls `__mcount_internal' (a normal C function) with two
1575 Number-of-calls information for library routines is collected by
1610 either calls `profil()' or sets up a clock signal handler. This
1617 (typically when `main' is called), calls `monstartup'.
1717 exactly which line of source code performed calls to a function.
1897 calls to each function are tallied
