Lines Matching full:each
162 how often each line of code executes
166 how much computing time each section of code uses
169 can look at each module to see which modules should be optimized.
186 places only one statement on each line. If you use complicated macros
193 indicates how many times each line of a source file \fI\fIsourcefile\fI.c\fR
237 each branch in your program was taken. Unconditional branches will not
286 Output summaries for each function in addition to the file level summary.
316 One \fI.gcov\fR file is produced for each source file containing code,
329 Additional block information may succeed each line, when requested by
366 Running the program will cause profile output to be generated. For each
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
451 the execution counts for individual blocks that end on that line. After each
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
512 branches and calls are each given a number. There is no simple way to map
530 number of times each line in the source was executed would be added to
538 exits. For each source file compiled with \fB\-fprofile\-arcs\fR, the
563 for each line because there isn't separate code for each line. Hence
596 each location might not be the same. For instance, a condition might
