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
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
87c2f9a5be
Revert "Auto merge of #130766 - clarfonthey:stable-coverage-attribute, r=wesleywiser"
...
This reverts commit 1d35638dc38dbfbf1cc2a9823135dfcf3c650169, reversing
changes made to f23a80a4c2fbca593b64e70f5970368824b4c5e9.
2024-12-23 12:30:37 +11:00
ltdk
cb487cc2fa
Stabilize #[coverage] attribute
2024-12-16 21:07:06 -05:00
Zalathar
ac815ff6b0
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-07 12:13:12 +11:00
Zalathar
44e4e4515c
coverage: Add an extra "transcribe" step after counter creation
2024-12-04 17:50:52 +11:00
Zalathar
2a3b4a0afd
coverage: Extract subtracted_sum in counter creation
2024-12-04 17:00:25 +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
40cfc2de77
coverage: Move branch coverage tests into a subdirectory
2024-04-17 11:41:40 +10:00
