about summary refs log tree commit diff
path: root/tests/coverage/mcdc
AgeCommit message (Collapse)AuthorLines
2025-08-06coverage: Remove all unstable support for MC/DC instrumentationZalathar-1826/+0
2025-05-06coverage: Only merge adjacent coverage spansZalathar-97/+137
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-20/+20
2025-04-05Update the minimum external LLVM to 19Josh Stone-50/+40
2025-04-01coverage: Shrink call spans to just the function nameZalathar-4/+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.
2025-01-16coverage: Completely overhaul counter assignment, using node-flow graphsZalathar-108/+97
2024-12-23Revert "Auto merge of #130766 - clarfonthey:stable-coverage-attribute, ↵Zalathar-40/+50
r=wesleywiser" This reverts commit 1d35638dc38dbfbf1cc2a9823135dfcf3c650169, reversing changes made to f23a80a4c2fbca593b64e70f5970368824b4c5e9.
2024-12-16Stabilize #[coverage] attributeltdk-50/+40
2024-12-07coverage: Prefer to visit nodes whose predecessors have been visitedZalathar-375/+252
2024-12-04coverage: Add an extra "transcribe" step after counter creationZalathar-407/+433
2024-11-08coverage: Restrict empty-span expansion to only cover `{` and `}`Zalathar-4/+4
2024-10-11coverage: Include the highest counter ID seen in `.cov-map` dumpsZalathar-0/+20
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-08coverage. Adapt to mcdc mapping formats introduced by llvm 19zhuyunxing-213/+107
2024-10-08coverage. Disable supporting mcdc on llvm-18zhuyunxing-10/+10
2024-09-18Update the minimum external LLVM to 18Josh Stone-52/+42
2024-08-01Finish blessing `coverage/mcdc` tests after LLVM 19 upgradeZalathar-0/+5
2024-07-30Bless coverage/mcdc for line number changesJosh Stone-42/+42
2024-07-30Disable MC/DC tests on LLVM 19Krasimir Georgiev-0/+5
Disable the tests and generate an error if MC/DC is used on LLVM 19. The support will be ported separately, as it is substantially different on LLVM 19, and there are no plans to support both versions.
2024-07-09coverage. Fix panic when generating mcdc code for inlined functionszhuyunxing-0/+79
2024-07-09coverage. MCDC tests also report branches coveragezhuyunxing-6/+78
2024-07-09coverage. Group mcdc tests in one directoryzhuyunxing-0/+1567
2024-05-29coverage: Add tests for the MC/DC condition limitZalathar-0/+270