rust/tests/coverage/mcdc/inlined_expressions.cov-map

Function name: inlined_expressions::inlined_instance
Raw bytes (52): 0x[01, 01, 03, 01, 05, 0b, 02, 09, 0d, 06, 01, 08, 01, 01, 06, 28, 03, 02, 01, 05, 00, 0b, 30, 05, 02, 01, 02, 00, 00, 05, 00, 06, 05, 00, 0a, 00, 0b, 30, 09, 0d, 02, 00, 00, 00, 0a, 00, 0b, 07, 01, 01, 00, 02]
Number of files: 1
- file 0 => global file 1
Number of expressions: 3
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
- expression 1 operands: lhs = Expression(2, Add), rhs = Expression(0, Sub)
- expression 2 operands: lhs = Counter(2), rhs = Counter(3)
Number of file 0 mappings: 6
- Code(Counter(0)) at (prev + 8, 1) to (start + 1, 6)
- MCDCDecision { bitmap_idx: 3, conditions_num: 2 } at (prev + 1, 5) to (start + 0, 11)
- MCDCBranch { true: Counter(1), false: Expression(0, Sub), condition_id: 1, true_next_id: 2, false_next_id: 0 } at (prev + 0, 5) to (start + 0, 6)
    true  = c1
    false = (c0 - c1)
- Code(Counter(1)) at (prev + 0, 10) to (start + 0, 11)
- MCDCBranch { true: Counter(2), false: Counter(3), condition_id: 2, true_next_id: 0, false_next_id: 0 } at (prev + 0, 10) to (start + 0, 11)
    true  = c2
    false = c3
- Code(Expression(1, Add)) at (prev + 1, 1) to (start + 0, 2)
    = ((c2 + c3) + (c0 - c1))
Highest counter ID seen: c3
coverage. Fix panic when generating mcdc code for inlined functions 2024-07-02 05:34:26 -05:00			`Function name: inlined_expressions::inlined_instance`
coverage. Adapt to mcdc mapping formats introduced by llvm 19 2024-07-25 02:23:35 -05:00			`Raw bytes (52): 0x[01, 01, 03, 01, 05, 0b, 02, 09, 0d, 06, 01, 08, 01, 01, 06, 28, 03, 02, 01, 05, 00, 0b, 30, 05, 02, 01, 02, 00, 00, 05, 00, 06, 05, 00, 0a, 00, 0b, 30, 09, 0d, 02, 00, 00, 00, 0a, 00, 0b, 07, 01, 01, 00, 02]`
coverage. Fix panic when generating mcdc code for inlined functions 2024-07-02 05:34:26 -05:00			`Number of files: 1`
			`- file 0 => global file 1`
			`Number of expressions: 3`
			`- expression 0 operands: lhs = Counter(0), rhs = Counter(1)`
			`- expression 1 operands: lhs = Expression(2, Add), rhs = Expression(0, Sub)`
			`- expression 2 operands: lhs = Counter(2), rhs = Counter(3)`
			`Number of file 0 mappings: 6`
Update the minimum external LLVM to 18 2024-09-17 14:37:45 -05:00			`- Code(Counter(0)) at (prev + 8, 1) to (start + 1, 6)`
coverage. Adapt to mcdc mapping formats introduced by llvm 19 2024-07-25 02:23:35 -05:00			`- MCDCDecision { bitmap_idx: 3, conditions_num: 2 } at (prev + 1, 5) to (start + 0, 11)`
coverage. Fix panic when generating mcdc code for inlined functions 2024-07-02 05:34:26 -05:00			`- MCDCBranch { true: Counter(1), false: Expression(0, Sub), condition_id: 1, true_next_id: 2, false_next_id: 0 } at (prev + 0, 5) to (start + 0, 6)`
			`true = c1`
			`false = (c0 - c1)`
			`- Code(Counter(1)) at (prev + 0, 10) to (start + 0, 11)`
			`- MCDCBranch { true: Counter(2), false: Counter(3), condition_id: 2, true_next_id: 0, false_next_id: 0 } at (prev + 0, 10) to (start + 0, 11)`
			`true = c2`
			`false = c3`
			`- Code(Expression(1, Add)) at (prev + 1, 1) to (start + 0, 2)`
			`= ((c2 + c3) + (c0 - c1))`
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-07 21:13:05 -05:00			`Highest counter ID seen: c3`
coverage. Fix panic when generating mcdc code for inlined functions 2024-07-02 05:34:26 -05:00