Home | History | Annotate | Download | only in man1

Lines Matching full:line

162 how often each line of code executes
184 time. Likewise, because \fBgcov\fR accumulates statistics by line (at
186 places only one statement on each line. If you use complicated macros
188 less helpful\-\-\-they only report on the line where the macro call
193 indicates how many times each line of a source file \fI\fIsourcefile\fI.c\fR
226 outputs execution counts only for the main blocks of a line. With this
227 option you can determine if blocks within a single line are not being
326 \& <execution_count>:<line_number>:<source line text>
329 Additional block information may succeed each line, when requested by
330 command line option. The \fIexecution_count\fR is \fB\-\fR for lines
342 unchanged. Use \fItag\fR to locate a particular preamble line.
372 for each line. For example, if your program is called \fItmp.c\fR, this
446 In this mode, each basic block is only shown on one line \*(-- the last
447 line of the block. A multi-line block will only contribute to the
448 execution count of that last line, and other lines will not be shown
450 The total execution count of a line is shown and subsequent lines show
451 the execution counts for individual blocks that end on that line. After each
456 after a line with no individual blocks.
457 As you can see, line 13 contains a basic block that was not executed.
504 For each function, a line is printed showing how many times the function
508 For each basic block, a line is printed after the last line of the basic
510 be multiple branches and calls listed for a single source line if there
511 are multiple basic blocks that end on that line. In this case, the
515 on the source line.
530 number of times each line in the source was executed would be added to
548 other \s-1GCC\s0 options; but if you want to prove that every single line
563 for each line because there isn't separate code for each line. Hence
580 Inlineable functions can create unexpected line counts. Line counts are
584 If the function is not inlined, the compiler must emit an out of line
586 \&\fIfileA.o\fR and \fIfileB.o\fR both contain out of line bodies of a
590 out of line bodies for all calls to that function, and remove or ignore
599 same source lines, the line counts themselves might seem inconsistent.