Lines Matching refs:coverage
1 llvm-cov - emit coverage information
14 The :program:`llvm-cov` tool shows code coverage information for
16 work with ``gcov``\-style coverage or with ``clang``\'s instrumentation
46 The :program:`llvm-cov gcov` tool reads code coverage data files and displays
47 the coverage information for a specified source file. It is compatible with the
52 of your application that collects coverage data as it runs. Compile with the
53 ``-fprofile-arcs`` and ``-ftest-coverage`` options to add the
54 instrumentation. (Alternatively, you can use the ``--coverage`` option, which
59 coverage data. The other half of the data comes from ``.gcda`` files that are
76 Once you have generated the coverage data files, run :program:`llvm-cov gcov`
77 for each main source file where you want to examine the coverage results. This
112 Show a summary of coverage for each function instead of just one summary for
121 For coverage output of files included from the main source file, add the
134 object file, the coverage data files are expected to have the same base name
141 Preserve path components when naming the coverage output files. In addition
172 Use md5 hash of file name when naming the coverage output files. The source
196 The :program:`llvm-cov show` command shows line by line coverage of the
198 filtered to only show the coverage for the files listed in *SOURCES*.
204 instrumentation to emit profile and coverage data. To build such a program with
209 The coverage information is stored in the built executable or library itself,
222 Show coverage for branch conditions in terms of either count or percentage.
266 Show code coverage only for functions with the given name.
270 Show code coverage only for functions listed in the given file. Each line in
276 Show code coverage only for functions listed in the given file. Each line in
283 Show code coverage only for functions that match the given regular expression.
300 Specify a directory to write coverage reports into. If the directory does not
322 Directory used as a base for relative coverage mapping paths. Only applicable
326 .. option:: -line-coverage-gt=<N>
328 Show code coverage only for functions with line coverage greater than the
331 .. option:: -line-coverage-lt=<N>
333 Show code coverage only for functions with line coverage less than the given
336 .. option:: -region-coverage-gt=<N>
338 Show code coverage only for functions with region coverage greater than the
341 .. option:: -region-coverage-lt=<N>
343 Show code coverage only for functions with region coverage less than the given
348 Map the paths in the coverage data to local source file paths. This allows you
349 to generate the coverage data on one machine, and then use llvm-cov on a
352 .. option:: -coverage-watermark=<high>,<low>
354 Set high and low watermarks for coverage in html format output. This allows you
355 to set the high and low watermark of coverage as desired, green when
356 coverage >= high, red when coverage < low, and yellow otherwise. Both high and
374 The :program:`llvm-cov report` command displays a summary of the coverage of
376 filtered to only show the coverage for the files listed in *SOURCES*.
382 coverage data. If any files are provided, summaries can be shown for each
385 For information on compiling programs for coverage and generating profile data,
412 Show coverage summaries for each function. Defaults to false.
424 Directory used as a base for relative coverage mapping paths. Only applicable
443 The :program:`llvm-cov export` command exports coverage data of the binaries
448 summaries of the coverage data will be exported. When exporting an lcov trace
449 file, the line-based coverage, branch coverage, and summaries will be exported.
451 The exported data can optionally be filtered to only export the coverage
454 For information on compiling programs for coverage and generating profile data,
474 Export only summary information for each file in the coverage data. This mode
475 will not export coverage information for smaller units such as individual
486 Skip exporting macro expansion coverage data.
490 Skip exporting per-function coverage data.
494 Use N threads to export coverage data. When N=0, llvm-cov auto-detects an
499 Directory used as a base for relative coverage mapping paths. Only applicable