about summary refs log tree commit diff
path: root/tests/coverage/unreachable.cov-map
AgeCommit message (Collapse)AuthorLines
2025-05-06coverage: Only merge adjacent coverage spansZalathar-8/+10
This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-05-06coverage-dump: Dump filenames instead of global file IDs (and bless)Zalathar-3/+3
2025-04-01coverage: Shrink call spans to just the function nameZalathar-6/+6
This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2024-12-16Stabilize #[coverage] attributeltdk-6/+6
2024-10-11coverage: Include the highest counter ID seen in `.cov-map` dumpsZalathar-0/+3
When making changes that have a large impact on coverage counter creation, this makes it easier to see whether the number of physical counters has changed. (The highest counter ID seen in coverage maps is not necessarily the same as the number of physical counters actually used by the instrumented code, but it's the best approximation we can get from looking only at the coverage maps, and it should be reasonably accurate in most cases.)
2024-03-27Eliminate `UbCheck` for non-standard librariesDianQK-6/+6
2024-03-26coverage: Re-enable `UnreachablePropagation` for coverage buildsZalathar-3/+3
2023-12-03coverage: Skip spans that can't be un-expanded back to the function bodyZalathar-6/+6
When we extract coverage spans from MIR, we try to "un-expand" them back to spans that are inside the function's body span. In cases where that doesn't succeed, the current code just swaps in the entire body span instead. But that tends to result in coverage spans that are completely unrelated to the control flow of the affected code, so it's better to just discard those spans.
2023-11-07coverage: Migrate `tests/coverage-map` into `tests/coverage`Zalathar-0/+24