Lines Matching full:each
163 how often each line of code executes
167 how much computing time each section of code uses
170 can look at each module to see which modules should be optimized.
187 places only one statement on each line. If you use complicated macros
194 indicates how many times each line of a source file \fI\fIsourcefile\fI.c\fR
238 each branch in your program was taken. Unconditional branches will not
287 Output summaries for each function in addition to the file level summary.
326 One \fI.gcov\fR file is produced for each source file containing code,
339 Additional block information may succeed each line, when requested by
376 Running the program will cause profile output to be generated. For each
382 for each line. For example, if your program is called \fItmp.c\fR, this
456 In this mode, each basic block is only shown on one line \*(-- the last
461 the execution counts for individual blocks that end on that line. After each
514 For each function, a line is printed showing how many times the function
518 For each basic block, a line is printed after the last line of the basic
522 branches and calls are each given a number. There is no simple way to map
540 number of times each line in the source was executed would be added to
548 exits. For each source file compiled with \fB\-fprofile\-arcs\fR, the
573 for each line because there isn't separate code for each line. Hence
606 each location might not be the same. For instance, a condition might
