| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2024-12-07 | coverage: Prefer to visit nodes whose predecessors have been visited | Zalathar | -77/+55 | |
| 2024-12-04 | coverage: Add an extra "transcribe" step after counter creation | Zalathar | -85/+85 | |
| 2024-10-11 | coverage: Include the highest counter ID seen in `.cov-map` dumps | Zalathar | -0/+4 | |
| 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-05-14 | coverage: Simplify counter expressions using simple algebra | Zalathar | -59/+48 | |
| Some of these cases currently don't occur in practice, but are included for completeness, and to avoid having to add them later as branch coverage and MC/DC coverage start building more complex expressions. | ||||
| 2024-04-17 | coverage: Branch coverage tests for lazy boolean operators | Zalathar | -0/+177 | |
