Lines Matching full:each
164 how often each line of code executes
168 how much computing time each section of code uses
171 can look at each module to see which modules should be optimized.
188 places only one statement on each line. If you use complicated macros
195 indicates how many times each line of a source file \fI\fIsourcefile\fI.c\fR
239 each branch in your program was taken. Unconditional branches will not
302 Output summaries for each function in addition to the file level summary.
341 One \fI.gcov\fR file is produced for each source file containing code,
354 Additional block information may succeed each line, when requested by
391 Running the program will cause profile output to be generated. For each
397 for each line. For example, if your program is called \fItmp.c\fR, this
471 In this mode, each basic block is only shown on one line \*(-- the last
476 the execution counts for individual blocks that end on that line. After each
529 For each function, a line is printed showing how many times the function
533 For each basic block, a line is printed after the last line of the basic
537 branches and calls are each given a number. There is no simple way to map
555 number of times each line in the source was executed would be added to
563 exits. For each source file compiled with \fB\-fprofile\-arcs\fR, the
588 for each line because there isn't separate code for each line. Hence
621 each location might not be the same. For instance, a condition might
