6 commits

Author	SHA1	Message	Date
Zalathar	26cea8a286	coverage: Don't split bang-macro spans, just truncate them	2025-04-01 13:13:21 +11:00
Zalathar	f1300c860e	coverage: Completely overhaul counter assignment, using node-flow graphs	2025-01-16 22:07:18 +11:00
Zalathar	44e4e4515c	coverage: Add an extra "transcribe" step after counter creation	2024-12-04 17:50:52 +11:00
Zalathar	3c30fe3423	coverage: Restrict empty-span expansion to only cover { and }	2024-11-08 20:43:08 +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
Zalathar	49127c64d6	coverage: Migrate tests/coverage-map into tests/coverage	2023-11-07 11:15:19 +11:00

Renamed from tests/coverage-map/panic_unwind.cov-map (Browse further)