| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2025-05-06 | coverage: Only merge adjacent coverage spans | Zalathar | -9/+15 | |
| This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans. | ||||
| 2025-05-06 | coverage-dump: Dump filenames instead of global file IDs (and bless) | Zalathar | -2/+2 | |
| 2025-01-16 | coverage: Completely overhaul counter assignment, using node-flow graphs | Zalathar | -24/+21 | |
| 2024-12-04 | coverage: Add an extra "transcribe" step after counter creation | Zalathar | -15/+16 | |
| 2024-11-08 | coverage: Restrict empty-span expansion to only cover `{` and `}` | Zalathar | -2/+2 | |
| 2024-10-11 | coverage: Include the highest counter ID seen in `.cov-map` dumps | Zalathar | -0/+2 | |
| 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.) | ||||
| 2023-11-07 | coverage: Migrate `tests/coverage-map` into `tests/coverage` | Zalathar | -0/+40 | |
