Pirama Arumuga Nainar 7b5dc69f32 [CoverageMapping] Handle gaps in counter IDs for source-based coverage ... For source-based coverage, the frontend sets the counter IDs and the constraints of counter IDs is not defined. For e.g., the Rust frontend until recently had a reserved counter #0 (https://github.com/rust-lang/rust/pull/83774). Rust coverage instrumentation also creates counters on edges in addition to basic blocks. Some functions may have more counters than regions. This breaks an assumption in CoverageMapping.cpp where the number of counters in a function is assumed to be bounded by the number of regions: Counts.assign(Record.MappingRegions.size(), 0); This assumption causes CounterMappingContext::evaluate() to fail since there are not enough counter values created in the above call to `Counts.assign`. Consequently, some uncovered functions are not reported in coverage reports. This change walks a Function's CoverageMappingRecord to find the maximum counter ID, and uses it to initialize the counter array when instrprof records are missing for a function in sparse profiles. Differential Revision: https://reviews.llvm.org/D101780		2021-05-19 10:46:38 -07:00
..
CMakeLists.txt
CoverageMappingTest.cpp	[CoverageMapping] Handle gaps in counter IDs for source-based coverage	2021-05-19 10:46:38 -07:00
InstrProfDataTest.cpp
InstrProfTest.cpp
SampleProfTest.cpp