Lines Matching +refs:clang +refs:format +refs:region

11 This document explains how to use clang's source-based code coverage feature.
62     % clang++ -fprofile-instr-generate -fcoverage-mapping foo.cc -o foo
132 …% clang++ -fprofile-instr-generate -fcoverage-mapping -mllvm -runtime-counter-relocation foo.cc -o…
158 region counts (even in macro expansions):
184 region counts:
271   least once. A code region may span multiple lines (e.g in a large function
285 implies 100% region coverage for a function. The project-wide totals for each
292   profile format. Raw profiles may be dependent on the specific compiler
297   These formats are not forwards-compatible: i.e, a tool which uses format
298   version X will not be able to understand format version (X+k).
300 * Tools must also retain **backwards** compatibility with the format of the
304 * The JSON coverage export format has a (major, minor, patch) version triple.
416 the clang code coverage implementation.
422 execution count to the count from a gap region unless that region is the only
452 The region mapping for a switch body consists of a gap region that covers the
454 last case ends). This gap region has a zero count: this causes "gap" areas in
457 When a switch case is visited, the parent region is extended: if the parent
458 region has no start location, its start location becomes the start of the case.
462 For switches with ``CompoundStmt`` bodies, a new region is created at the start
467 branch region is generated to correspond to the implicit default case that is
468 generated by the compiler.  The implicit branch region is tied to the line and