Lines Matching refs:functions
122 [ --display-unused-functions ] [ --file-format=@var{name} ]
127 [ --width=@var{n} ] [ --ignore-non-functions ]
207 functions called which other functions while it was executing. This
210 execute faster. It can also tell you which functions are being called more
245 which functions burn most of the cycles, it is stated concisely here.
248 The @dfn{call graph} shows, for each function, which functions called it, which
249 other functions it called, and how many times. There is also an estimate
320 standard library functions such as @code{read} and @code{open}. For
344 you get for the functions in those modules is the total time spent in them;
347 the functions will be blank), but will greatly reduce the usefulness of the
360 @samp{-finstrument-functions} command line option which will insert
456 * Symspecs:: Specifying functions to include or exclude
467 functions to be included or excluded. These options can be
473 for all functions.
493 print a tally of functions and the number of times each was called.
578 print a tally of functions and the number of times each was called.
587 ordering of functions in an executable.
589 The exact details of how to force the linker to place functions
599 ordering of functions in an executable.
661 statically declared (private) functions. (These are functions whose
664 functions, calls to/from them, etc., will all be attributed to the
674 Since normal call graph records are only generated when functions are
676 but never were. Calls to functions that were not compiled with
685 @itemx --ignore-non-functions
687 are not known to be functions. This option will give more accurate
699 instead of functions. This feature only works with programs compiled
740 @itemx --display-unused-functions
742 functions in the flat profile, even those that were never called, and
799 as a child of any functions that call it, but its index number will be
839 lists in the call graph all functions that were reached from either
845 Many of the output options allow functions to be included or excluded
869 Selects all functions named @samp{main}.
908 * Call Graph:: The call graph shows which functions called which
923 functions with no apparent time spent in them, and no apparent calls
957 The functions are sorted first by decreasing run-time spent in them,
959 functions @samp{mcount} and @samp{profil} are part of the profiling
985 The remaining functions in the listing (those whose
990 Clearly some time was spent executing these functions,
1003 executing this functions, plus the time spent in all the functions
1038 and its children. From this information, you can find functions that,
1040 functions that did use unusual amounts of time.
1219 Not all functions have entries in the call graph; some
1220 options to @code{gprof} request the omission of certain functions.
1222 in the entries of the functions it calls.
1295 Whenever there are call paths both ways between a pair of functions, they
1315 total time spent directly in the functions of the cycle. The
1316 ``subroutines'' of the cycle are the individual functions of the cycle, and
1317 all other functions that were called directly by them. The ``callers'' of
1318 the cycle are the functions, outside the cycle, that called functions in
1322 functions @code{a} and @code{b}. The cycle was entered by a call to
1385 spent in all the functions of the cycle. It equals the sum of the
1386 @code{self} fields for the individual functions in the cycle, found
1387 in the entry in the subroutine lines for these functions.
1401 first, the number of times functions in the cycle were called by functions
1403 functions in the cycle (including times when a function in the cycle calls
1408 cycle's entry says how many time that function was called from functions in
1412 In the individual entry for a function in a cycle, the other functions in
1424 samples are assigned not to functions, but to individual
1725 is spending its time is to re-factor large functions into sequences
1784 @code{gprof} still lists it as a subroutine of functions that call it.
2180 the functions with the most use and the most parents are
2181 placed first, followed by other functions with the most use,
2182 followed by lower use functions, followed by unused functions