Lines Matching full:coverage

32 llvm-cov \- emit coverage information
38 The \fBllvm\-cov\fP tool shows code coverage information for
40 work with \fBgcov\fP\-style coverage or with \fBclang\fP\(aqs instrumentation
63 The \fBllvm\-cov gcov\fP tool reads code coverage data files and displays
64 the coverage information for a specified source file. It is compatible with the
69 of your application that collects coverage data as it runs. Compile with the
70 \fB\-fprofile\-arcs\fP and \fB\-ftest\-coverage\fP options to add the
71 instrumentation. (Alternatively, you can use the \fB\-\-coverage\fP option, which
76 coverage data. The other half of the data comes from \fB\&.gcda\fP files that are
93 Once you have generated the coverage data files, run \fBllvm\-cov gcov\fP
94 for each main source file where you want to examine the coverage results. This
131 Show a summary of coverage for each function instead of just one summary for
142 For coverage output of files included from the main source file, add the
157 object file, the coverage data files are expected to have the same base name
165 Preserve path components when naming the coverage output files. In addition
202 Use md5 hash of file name when naming the coverage output files. The source
215 The \fBllvm\-cov show\fP command shows line by line coverage of the
217 filtered to only show the coverage for the files listed in \fISOURCE\fP\&....
223 instrumentation to emit profile and coverage data. To build such a program with
228 The coverage information is stored in the built executable or library itself,
239 Show coverage for branch conditions in terms of either count or percentage.
291 Show code coverage only for functions with the given name.
296 Show code coverage only for functions listed in the given file. Each line in
303 Show code coverage only for functions that match the given regular expression.
324 Specify a directory to write coverage reports into. If the directory does not
349 Directory used as a base for relative coverage mapping paths. Only applicable
355 .B \-line\-coverage\-gt=<N>
356 Show code coverage only for functions with line coverage greater than the
361 .B \-line\-coverage\-lt=<N>
362 Show code coverage only for functions with line coverage less than the given
367 .B \-region\-coverage\-gt=<N>
368 Show code coverage only for functions with region coverage greater than the
373 .B \-region\-coverage\-lt=<N>
374 Show code coverage only for functions with region coverage less than the given
380 Map the paths in the coverage data to local source file paths. This allows you
381 to generate the coverage data on one machine, and then use llvm\-cov on a
386 .B \-coverage\-watermark=<high>,<low>
387 Set high and low watermarks for coverage in html format output. This allows you
388 to set the high and low watermark of coverage as desired, green when
389 coverage >= high, red when coverage < low, and yellow otherwise. Both high and
397 Use debuginfod to look up coverage mapping for binary IDs present in the profile
413 The \fBllvm\-cov report\fP command displays a summary of the coverage of
415 filtered to only show the coverage for the files listed in \fISOURCE\fP\&....
421 coverage data. If any files are provided, summaries can be shown for each
424 For information on compiling programs for coverage and generating profile data,
453 Show coverage summaries for each function. Defaults to false.
468 Directory used as a base for relative coverage mapping paths. Only applicable
477 Attempt to look up coverage mapping from objects using debuginfod. This is
494 The \fBllvm\-cov export\fP command exports coverage data of the binaries
499 summaries of the coverage data will be exported. When exporting an lcov trace
500 file, the line\-based coverage, branch coverage, and summaries will be exported.
502 The exported data can optionally be filtered to only export the coverage
505 For information on compiling programs for coverage and generating profile data,
525 Export only summary information for each file in the coverage data. This mode
526 will not export coverage information for smaller units such as individual
540 Skip exporting macro expansion coverage data.
546 Skip exporting per\-function coverage data.
552 Use N threads to export coverage data. When N=0, llvm\-cov auto\-detects an
558 Directory used as a base for relative coverage mapping paths. Only applicable
567 Attempt to look up coverage mapping from objects using debuginfod. This is