Lines Matching full:each
165 how often each line of code executes
169 how much computing time each section of code uses
172 can look at each module to see which modules should be optimized.
189 places only one statement on each line. If you use complicated macros
196 indicates how many times each line of a source file \fI\fIsourcefile\fI.c\fR
240 each branch in your program was taken. Unconditional branches will not
303 Output summaries for each function in addition to the file level summary.
342 One \fI.gcov\fR file is produced for each source file containing code,
355 Additional block information may succeed each line, when requested by
392 Running the program will cause profile output to be generated. For each
398 for each line. For example, if your program is called \fItmp.c\fR, this
472 In this mode, each basic block is only shown on one line \*(-- the last
477 the execution counts for individual blocks that end on that line. After each
530 For each function, a line is printed showing how many times the function
534 For each basic block, a line is printed after the last line of the basic
538 branches and calls are each given a number. There is no simple way to map
556 number of times each line in the source was executed would be added to
564 exits. For each source file compiled with \fB\-fprofile\-arcs\fR, the
589 for each line because there isn't separate code for each line. Hence
622 each location might not be the same. For instance, a condition might
