Lines Matching full:line
102 code, labeled with the number of times each line of the program was
174 If you wish to perform line-by-line profiling you should use the
178 Note, older versions of `gcc' produce line-by-line profiling
181 Line-by-line Profiling: Line-by-line.
184 `-finstrument-functions' command line option which will insert calls to
240 `gprof' command line, _along with `gmon.out'_, like this:
411 .o link line ordering for the program based on profiling data.
448 If this option is specified, every line in a basic-block is
449 annotated by repeating the annotation for the first line. This
504 `--line'
505 The `-l' option enables line-by-line profiling, which causes
512 this option will also identify how many times each line of code
513 was executed. While line-by-line profiling can help isolate where
556 The `-h' option prints command line usage.
679 Selects line 134 in file `main.c'.
700 * Line-by-line:: `gprof' can analyze individual source code lines
770 Here is what the fields in each line mean:
809 File: gprof.info, Node: Call Graph, Next: Line-by-line, Prev: Flat Profile, Up: Output
854 In each entry, the primary line is the one that starts with an index
855 number in square brackets. The end of this line says which function
868 * Primary:: Details of the primary line's contents.
877 5.2.1 The Primary Line
880 The "primary line" in a call graph entry is the line that describes the
884 For reference, we repeat the primary line from the entry for function
885 `report' in our main example, together with the heading line that shows
892 Here is what the fields in the primary line mean:
897 its primary line.
942 index number twelve, its primary line would be end like this:
952 A function's entry has a line for each function it was called by.
953 These lines' fields correspond to the fields of the primary line, but
957 `report', the primary line and one caller-line preceding it, together
958 with the heading line that shows the names of the fields:
965 Here are the meanings of the fields in the caller-line for `report'
985 The name of the caller of `report' to which this line applies,
997 dummy caller-line is printed which has `<spontaneous>' as the "caller's
1006 A function's entry has a line for each of its subroutines--in other
1007 words, a line for each other function that it called. These lines'
1008 fields correspond to the fields of the primary line, but their meanings
1012 `main', the primary line and a line for a subroutine, together with the
1013 heading line that shows the names of the fields:
1020 Here are the meanings of the fields in the subroutine-line for `main'
1042 The name of the subroutine of `main' to which this line applies,
1078 for the cycle as a whole. The primary line of this entry describes the
1143 The `self' field of the cycle's primary line is the total time spent
1148 The `children' fields of the cycle's primary line and subroutine
1155 The `children' field of a caller-line in the cycle's entry estimates
1160 The `called' field in the primary line for the cycle has two numbers:
1167 The `called' field of a subroutine-line for a cycle member in the
1170 the primary line's `called' field.
1180 File: gprof.info, Node: Line-by-line, Next: Annotated Source, Prev: Call Graph, Up: Output
1182 5.3 Line-by-line Profiling
1185 `gprof''s `-l' option causes the program to perform "line-by-line"
1190 line-by-line profiling information.
1196 line option as well.
1198 The flat profile is the most useful output table in line-by-line
1202 each line of code that called each function, along with a count.
1204 Here is a section of `gprof''s output, without line-by-line
1230 this time with line-by-line profiling enabled. Note that `ct_init''s
1234 one call from line 396, 3071 calls from line 384, 3730 calls from line
1270 File: gprof.info, Node: Annotated Source, Prev: Line-by-line, Up: Output
1283 times each line of code was executed. With newer versions of `gcc'
1288 line numbers added:
1311 itself. The `if' statement on line 9 generates two more basic-blocks,
1313 `if' on line 13, and the contents of the `do' loop form the fifth
1319 line of code is labeled at least once. Here is `updcrc''s annotated
1460 Looking at the per-line call counts only tells part of the story.
1474 callers will be broken down by function and line number.
1512 number of recursive calls in the primary line.
1521 blocks on the same line, GNU `gprof' prints all of their counts,
1714 function. However, when profiling at the line-level, it is better if
1716 This will ensure that the line-level call-graph is able to identify
1717 exactly which line of source code performed calls to a function.
1749 lists EXCL_TIME and EXCL_GRAPH, and if line-by-line profiling is
1762 whether line-by-line profiling (`-l' option) has been enabled. For
1764 line-by-line profiling, every text space address is examined, and a new
1765 symbol table entry gets created every time the line number changes. In
1779 Line number symbols have no special flags set. Additionally, a symbol
1819 only if line-by-line profiling has been selected. Each basic-block
1820 address is matched to a corresponding line symbol in the symbol table,
1836 profiling, but overlaps are more common during line-by-line profiling,
1869 if present, to label each line of code with call counts, otherwise only
1909 file. For line-by-line profiling (`-l' option), also shows line
2326 Node: Line-by-line50397
