6 Commits

Author	SHA1	Message	Date
Zalathar	4d5a1acebf	coverage: Only merge adjacent coverage spans ... 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 20:42:25 +10:00
Zalathar	c53a76743c	coverage-dump: Dump filenames instead of global file IDs (and bless)	2025-05-06 11:58:58 +10:00
Zalathar	bf1f254b13	coverage: Don't create counters for code that was removed by MIR opts	2025-02-06 21:44:31 +11:00
Zalathar	599f95ecc2	coverage: Include the highest counter ID seen in .cov-map dumps ... 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-10-11 21:04:37 +11:00
Vadim Petrochenkov	9f8d05f29f	macro_rules: Preserve all metavariable spans in a global side table	2024-02-18 11:19:24 +03:00
Zalathar	e0de143970	coverage: Regression test for markers in a function with no spans	2023-12-16 11:10:11 +11:00