Lines Matching full:line
103 code, labeled with the number of times each line of the program was
175 If you wish to perform line-by-line profiling you should use the
179 Note, older versions of `gcc' produce line-by-line profiling
182 Line-by-line Profiling: Line-by-line.
185 `-finstrument-functions' command line option which will insert calls to
241 `gprof' command line, _along with `gmon.out'_, like this:
412 .o link line ordering for the program based on profiling data.
449 If this option is specified, every line in a basic-block is
450 annotated by repeating the annotation for the first line. This
505 `--line'
506 The `-l' option enables line-by-line profiling, which causes
513 this option will also identify how many times each line of code
514 was executed. While line-by-line profiling can help isolate where
557 The `-h' option prints command line usage.
680 Selects line 134 in file `main.c'.
701 * Line-by-line:: `gprof' can analyze individual source code lines
771 Here is what the fields in each line mean:
810 File: gprof.info, Node: Call Graph, Next: Line-by-line, Prev: Flat Profile, Up: Output
855 In each entry, the primary line is the one that starts with an index
856 number in square brackets. The end of this line says which function
869 * Primary:: Details of the primary line's contents.
878 5.2.1 The Primary Line
881 The "primary line" in a call graph entry is the line that describes the
885 For reference, we repeat the primary line from the entry for function
886 `report' in our main example, together with the heading line that shows
893 Here is what the fields in the primary line mean:
898 its primary line.
943 index number twelve, its primary line would be end like this:
953 A function's entry has a line for each function it was called by.
954 These lines' fields correspond to the fields of the primary line, but
958 `report', the primary line and one caller-line preceding it, together
959 with the heading line that shows the names of the fields:
966 Here are the meanings of the fields in the caller-line for `report'
986 The name of the caller of `report' to which this line applies,
998 dummy caller-line is printed which has `<spontaneous>' as the "caller's
1007 A function's entry has a line for each of its subroutines--in other
1008 words, a line for each other function that it called. These lines'
1009 fields correspond to the fields of the primary line, but their meanings
1013 `main', the primary line and a line for a subroutine, together with the
1014 heading line that shows the names of the fields:
1021 Here are the meanings of the fields in the subroutine-line for `main'
1043 The name of the subroutine of `main' to which this line applies,
1079 for the cycle as a whole. The primary line of this entry describes the
1144 The `self' field of the cycle's primary line is the total time spent
1149 The `children' fields of the cycle's primary line and subroutine
1156 The `children' field of a caller-line in the cycle's entry estimates
1161 The `called' field in the primary line for the cycle has two numbers:
1168 The `called' field of a subroutine-line for a cycle member in the
1171 the primary line's `called' field.
1181 File: gprof.info, Node: Line-by-line, Next: Annotated Source, Prev: Call Graph, Up: Output
1183 5.3 Line-by-line Profiling
1186 `gprof''s `-l' option causes the program to perform "line-by-line"
1191 line-by-line profiling information.
1197 line option as well.
1199 The flat profile is the most useful output table in line-by-line
1203 each line of code that called each function, along with a count.
1205 Here is a section of `gprof''s output, without line-by-line
1231 this time with line-by-line profiling enabled. Note that `ct_init''s
1235 one call from line 396, 3071 calls from line 384, 3730 calls from line
1271 File: gprof.info, Node: Annotated Source, Prev: Line-by-line, Up: Output
1284 times each line of code was executed. With newer versions of `gcc'
1289 line numbers added:
1312 itself. The `if' statement on line 9 generates two more basic-blocks,
1314 `if' on line 13, and the contents of the `do' loop form the fifth
1320 line of code is labeled at least once. Here is `updcrc''s annotated
1461 Looking at the per-line call counts only tells part of the story.
1475 callers will be broken down by function and line number.
1513 number of recursive calls in the primary line.
1522 blocks on the same line, GNU `gprof' prints all of their counts,
1715 function. However, when profiling at the line-level, it is better if
1717 This will ensure that the line-level call-graph is able to identify
1718 exactly which line of source code performed calls to a function.
1750 lists EXCL_TIME and EXCL_GRAPH, and if line-by-line profiling is
1763 whether line-by-line profiling (`-l' option) has been enabled. For
1765 line-by-line profiling, every text space address is examined, and a new
1766 symbol table entry gets created every time the line number changes. In
1780 Line number symbols have no special flags set. Additionally, a symbol
1820 only if line-by-line profiling has been selected. Each basic-block
1821 address is matched to a corresponding line symbol in the symbol table,
1837 profiling, but overlaps are more common during line-by-line profiling,
1870 if present, to label each line of code with call counts, otherwise only
1910 file. For line-by-line profiling (`-l' option), also shows line
2327 Node: Line-by-line50458
