Lines Matching refs:times

149 Next, these times are propagated along the edges of the call graph.
160 by the number of times the function is called.
162 parents is directly proportional to the number of times that
171 Any profiled children of signal catchers should have their times
244 and how many times that function was called.  If you simply want to know
249 other functions it called, and how many times.  There is also an estimate
255 source code, labeled with the number of times each line of the
345 there is no record of how many times they were called, or from where.  This
468 specified multiple times, with different symspecs, to include
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.
704 this option will also identify how many times each line of
720 Symbols that are executed less than @var{num} times are suppressed.
725 to only propagate times for symbols matching @var{symspec}.
730 not to propagate times for symbols matching @var{symspec}.
1011 This is the total number of times the function was called.  If the
1012 function was never called, or the number of times it was called cannot
1152 This is the number of times the function was called.
1211 Two numbers: the number of times @code{report} was called from @code{main},
1398 subroutines, on the times when that caller called a function in the cycle.
1401 first, the number of times functions in the cycle were called by functions
1402 outside the cycle; second, the number of times they were called by
1403 functions in the cycle (including times when a function in the cycle calls
1414 how many times each function in the cycle called or was called from each other
1522 number of times it was called.  You may also need to specify the
1528 determine how many times each line of code was executed.  With newer
1597 loop was executed a total of 26312 times.  Note how the @code{while}
1598 statement is annotated.  It began execution 26312 times, once for
1599 each iteration through the loop.  One of those times (the last time)
1600 it exited, while it branched back to the beginning of the loop 26311 times.
1607 * Assumptions::         Estimating children times
1617 chance it will actually find that function zero times, or twice.
1723 Because @code{gprof} can only report call times and counts by function,
1731 @item How do I find which lines in my program were executed the most times?
1824 called it, and can count how many times it was called.  This change is made
1842 and the number of times each of these call arcs was traversed.
1859 Typically the program counter is looked at around 100 times per second of
1911 along with the number of times it was executed.
1990 and a count indicating the number of times the arc was traversed
2006 identifies a basic-block and the count specifies the number of times
2216 Shows how function times are propagated along the call graph