mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
rust/tests/coverage/loops_branches.cov-map

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

171 lines
11 KiB
Plaintext
Raw Permalink Normal View History

Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
Function name: <loops_branches::DebugTest as core::fmt::Debug>::fmt
coverage: Restrict empty-span expansion to only cover `{` and `}`
2024-11-05 04:59:10 -06:00
Raw bytes (228): 0x[01, 01, 2a, 05, 00, 9f, 01, 19, a3, 01, a7, 01, 0d, 00, 11, 00, a3, 01, a7, 01, 0d, 00, 11, 00, 9f, 01, 19, a3, 01, a7, 01, 0d, 00, 11, 00, 9a, 01, 00, 9f, 01, 19, a3, 01, a7, 01, 0d, 00, 11, 00, 96, 01, 00, 9a, 01, 00, 9f, 01, 19, a3, 01, a7, 01, 0d, 00, 11, 00, 9a, 01, 00, 9f, 01, 19, a3, 01, a7, 01, 0d, 00, 11, 00, 96, 01, 11, 9a, 01, 00, 9f, 01, 19, a3, 01, a7, 01, 0d, 00, 11, 00, 8f, 01, 19, 25, 92, 01, 96, 01, 11, 9a, 01, 00, 9f, 01, 19, a3, 01, a7, 01, 0d, 00, 11, 00, 14, 01, 09, 05, 01, 10, 05, 02, 10, 00, 15, 00, 01, 17, 00, 1b, 00, 00, 1c, 00, 1e, 02, 01, 0d, 00, 0e, 05, 01, 0d, 00, 1e, 25, 00, 1e, 00, 1f, 00, 01, 10, 01, 0a, 9a, 01, 03, 0d, 00, 0e, 9f, 01, 00, 12, 00, 17, 9a, 01, 01, 10, 00, 14, 96, 01, 01, 14, 00, 19, 00, 01, 1b, 00, 1f, 00, 00, 20, 00, 22, 46, 01, 11, 00, 12, 96, 01, 01, 11, 00, 22, 92, 01, 00, 22, 00, 23, 00, 01, 14, 01, 0e, 19, 03, 09, 00, 0f, 8b, 01, 01, 05, 00, 06]
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
Number of files: 1
- file 0 => global file 1
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
Number of expressions: 42
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
- expression 0 operands: lhs = Counter(1), rhs = Zero
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- expression 1 operands: lhs = Expression(39, Add), rhs = Counter(6)
- expression 2 operands: lhs = Expression(40, Add), rhs = Expression(41, Add)
- expression 3 operands: lhs = Counter(3), rhs = Zero
- expression 4 operands: lhs = Counter(4), rhs = Zero
- expression 5 operands: lhs = Expression(40, Add), rhs = Expression(41, Add)
- expression 6 operands: lhs = Counter(3), rhs = Zero
- expression 7 operands: lhs = Counter(4), rhs = Zero
- expression 8 operands: lhs = Expression(39, Add), rhs = Counter(6)
- expression 9 operands: lhs = Expression(40, Add), rhs = Expression(41, Add)
- expression 10 operands: lhs = Counter(3), rhs = Zero
- expression 11 operands: lhs = Counter(4), rhs = Zero
- expression 12 operands: lhs = Expression(38, Sub), rhs = Zero
- expression 13 operands: lhs = Expression(39, Add), rhs = Counter(6)
- expression 14 operands: lhs = Expression(40, Add), rhs = Expression(41, Add)
- expression 15 operands: lhs = Counter(3), rhs = Zero
- expression 16 operands: lhs = Counter(4), rhs = Zero
- expression 17 operands: lhs = Expression(37, Sub), rhs = Zero
- expression 18 operands: lhs = Expression(38, Sub), rhs = Zero
- expression 19 operands: lhs = Expression(39, Add), rhs = Counter(6)
- expression 20 operands: lhs = Expression(40, Add), rhs = Expression(41, Add)
- expression 21 operands: lhs = Counter(3), rhs = Zero
- expression 22 operands: lhs = Counter(4), rhs = Zero
- expression 23 operands: lhs = Expression(38, Sub), rhs = Zero
- expression 24 operands: lhs = Expression(39, Add), rhs = Counter(6)
- expression 25 operands: lhs = Expression(40, Add), rhs = Expression(41, Add)
- expression 26 operands: lhs = Counter(3), rhs = Zero
- expression 27 operands: lhs = Counter(4), rhs = Zero
- expression 28 operands: lhs = Expression(37, Sub), rhs = Counter(4)
- expression 29 operands: lhs = Expression(38, Sub), rhs = Zero
- expression 30 operands: lhs = Expression(39, Add), rhs = Counter(6)
- expression 31 operands: lhs = Expression(40, Add), rhs = Expression(41, Add)
- expression 32 operands: lhs = Counter(3), rhs = Zero
- expression 33 operands: lhs = Counter(4), rhs = Zero
- expression 34 operands: lhs = Expression(35, Add), rhs = Counter(6)
- expression 35 operands: lhs = Counter(9), rhs = Expression(36, Sub)
- expression 36 operands: lhs = Expression(37, Sub), rhs = Counter(4)
- expression 37 operands: lhs = Expression(38, Sub), rhs = Zero
- expression 38 operands: lhs = Expression(39, Add), rhs = Counter(6)
- expression 39 operands: lhs = Expression(40, Add), rhs = Expression(41, Add)
- expression 40 operands: lhs = Counter(3), rhs = Zero
- expression 41 operands: lhs = Counter(4), rhs = Zero
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
Number of file 0 mappings: 20
- Code(Counter(0)) at (prev + 9, 5) to (start + 1, 16)
- Code(Counter(1)) at (prev + 2, 16) to (start + 0, 21)
- Code(Zero) at (prev + 1, 23) to (start + 0, 27)
- Code(Zero) at (prev + 0, 28) to (start + 0, 30)
coverage: Restrict empty-span expansion to only cover `{` and `}`
2024-11-05 04:59:10 -06:00
- Code(Expression(0, Sub)) at (prev + 1, 13) to (start + 0, 14)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (c1 - Zero)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Counter(1)) at (prev + 1, 13) to (start + 0, 30)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
- Code(Counter(9)) at (prev + 0, 30) to (start + 0, 31)
- Code(Zero) at (prev + 1, 16) to (start + 1, 10)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(38, Sub)) at (prev + 3, 13) to (start + 0, 14)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (((c3 + Zero) + (c4 + Zero)) - c6)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(39, Add)) at (prev + 0, 18) to (start + 0, 23)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= ((c3 + Zero) + (c4 + Zero))
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(38, Sub)) at (prev + 1, 16) to (start + 0, 20)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (((c3 + Zero) + (c4 + Zero)) - c6)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(37, Sub)) at (prev + 1, 20) to (start + 0, 25)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= ((((c3 + Zero) + (c4 + Zero)) - c6) - Zero)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
- Code(Zero) at (prev + 1, 27) to (start + 0, 31)
- Code(Zero) at (prev + 0, 32) to (start + 0, 34)
coverage: Restrict empty-span expansion to only cover `{` and `}`
2024-11-05 04:59:10 -06:00
- Code(Expression(17, Sub)) at (prev + 1, 17) to (start + 0, 18)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (((((c3 + Zero) + (c4 + Zero)) - c6) - Zero) - Zero)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(37, Sub)) at (prev + 1, 17) to (start + 0, 34)
= ((((c3 + Zero) + (c4 + Zero)) - c6) - Zero)
- Code(Expression(36, Sub)) at (prev + 0, 34) to (start + 0, 35)
= (((((c3 + Zero) + (c4 + Zero)) - c6) - Zero) - c4)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
- Code(Zero) at (prev + 1, 20) to (start + 1, 14)
- Code(Counter(6)) at (prev + 3, 9) to (start + 0, 15)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(34, Add)) at (prev + 1, 5) to (start + 0, 6)
= ((c9 + (((((c3 + Zero) + (c4 + Zero)) - c6) - Zero) - c4)) + c6)
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: c9
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
Function name: <loops_branches::DisplayTest as core::fmt::Display>::fmt
coverage: Restrict empty-span expansion to only cover `{` and `}`
2024-11-05 04:59:10 -06:00
Raw bytes (230): 0x[01, 01, 2b, 01, 00, 02, 00, a3, 01, 19, a7, 01, ab, 01, 00, 0d, 00, 15, a7, 01, ab, 01, 00, 0d, 00, 15, a3, 01, 19, a7, 01, ab, 01, 00, 0d, 00, 15, 9e, 01, 00, a3, 01, 19, a7, 01, ab, 01, 00, 0d, 00, 15, 9a, 01, 00, 9e, 01, 00, a3, 01, 19, a7, 01, ab, 01, 00, 0d, 00, 15, 9e, 01, 00, a3, 01, 19, a7, 01, ab, 01, 00, 0d, 00, 15, 9a, 01, 15, 9e, 01, 00, a3, 01, 19, a7, 01, ab, 01, 00, 0d, 00, 15, 93, 01, 25, 96, 01, 19, 9a, 01, 15, 9e, 01, 00, a3, 01, 19, a7, 01, ab, 01, 00, 0d, 00, 15, 14, 01, 22, 05, 01, 11, 00, 01, 12, 01, 0a, 02, 02, 10, 00, 15, 00, 01, 17, 00, 1b, 00, 00, 1c, 00, 1e, 06, 01, 0d, 00, 0e, 02, 01, 0d, 00, 1e, 25, 00, 1e, 00, 1f, 9e, 01, 02, 0d, 00, 0e, a3, 01, 00, 12, 00, 17, 9e, 01, 01, 10, 00, 15, 00, 00, 16, 01, 0e, 9a, 01, 02, 14, 00, 19, 00, 01, 1b, 00, 1f, 00, 00, 20, 00, 22, 4a, 01, 11, 00, 12, 9a, 01, 01, 11, 00, 22, 96, 01, 00, 22, 00, 23, 19, 03, 09, 00, 0f, 8f, 01, 01, 05, 00, 06]
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
Number of files: 1
- file 0 => global file 1
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
Number of expressions: 43
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
- expression 0 operands: lhs = Counter(0), rhs = Zero
- expression 1 operands: lhs = Expression(0, Sub), rhs = Zero
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- expression 2 operands: lhs = Expression(40, Add), rhs = Counter(6)
- expression 3 operands: lhs = Expression(41, Add), rhs = Expression(42, Add)
- expression 4 operands: lhs = Zero, rhs = Counter(3)
- expression 5 operands: lhs = Zero, rhs = Counter(5)
- expression 6 operands: lhs = Expression(41, Add), rhs = Expression(42, Add)
- expression 7 operands: lhs = Zero, rhs = Counter(3)
- expression 8 operands: lhs = Zero, rhs = Counter(5)
- expression 9 operands: lhs = Expression(40, Add), rhs = Counter(6)
- expression 10 operands: lhs = Expression(41, Add), rhs = Expression(42, Add)
- expression 11 operands: lhs = Zero, rhs = Counter(3)
- expression 12 operands: lhs = Zero, rhs = Counter(5)
- expression 13 operands: lhs = Expression(39, Sub), rhs = Zero
- expression 14 operands: lhs = Expression(40, Add), rhs = Counter(6)
- expression 15 operands: lhs = Expression(41, Add), rhs = Expression(42, Add)
- expression 16 operands: lhs = Zero, rhs = Counter(3)
- expression 17 operands: lhs = Zero, rhs = Counter(5)
- expression 18 operands: lhs = Expression(38, Sub), rhs = Zero
- expression 19 operands: lhs = Expression(39, Sub), rhs = Zero
- expression 20 operands: lhs = Expression(40, Add), rhs = Counter(6)
- expression 21 operands: lhs = Expression(41, Add), rhs = Expression(42, Add)
- expression 22 operands: lhs = Zero, rhs = Counter(3)
- expression 23 operands: lhs = Zero, rhs = Counter(5)
- expression 24 operands: lhs = Expression(39, Sub), rhs = Zero
- expression 25 operands: lhs = Expression(40, Add), rhs = Counter(6)
- expression 26 operands: lhs = Expression(41, Add), rhs = Expression(42, Add)
- expression 27 operands: lhs = Zero, rhs = Counter(3)
- expression 28 operands: lhs = Zero, rhs = Counter(5)
- expression 29 operands: lhs = Expression(38, Sub), rhs = Counter(5)
- expression 30 operands: lhs = Expression(39, Sub), rhs = Zero
- expression 31 operands: lhs = Expression(40, Add), rhs = Counter(6)
- expression 32 operands: lhs = Expression(41, Add), rhs = Expression(42, Add)
- expression 33 operands: lhs = Zero, rhs = Counter(3)
- expression 34 operands: lhs = Zero, rhs = Counter(5)
- expression 35 operands: lhs = Expression(36, Add), rhs = Counter(9)
- expression 36 operands: lhs = Expression(37, Sub), rhs = Counter(6)
- expression 37 operands: lhs = Expression(38, Sub), rhs = Counter(5)
- expression 38 operands: lhs = Expression(39, Sub), rhs = Zero
- expression 39 operands: lhs = Expression(40, Add), rhs = Counter(6)
- expression 40 operands: lhs = Expression(41, Add), rhs = Expression(42, Add)
- expression 41 operands: lhs = Zero, rhs = Counter(3)
- expression 42 operands: lhs = Zero, rhs = Counter(5)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
Number of file 0 mappings: 20
- Code(Counter(0)) at (prev + 34, 5) to (start + 1, 17)
- Code(Zero) at (prev + 1, 18) to (start + 1, 10)
- Code(Expression(0, Sub)) at (prev + 2, 16) to (start + 0, 21)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (c0 - Zero)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
- Code(Zero) at (prev + 1, 23) to (start + 0, 27)
- Code(Zero) at (prev + 0, 28) to (start + 0, 30)
coverage: Restrict empty-span expansion to only cover `{` and `}`
2024-11-05 04:59:10 -06:00
- Code(Expression(1, Sub)) at (prev + 1, 13) to (start + 0, 14)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= ((c0 - Zero) - Zero)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(0, Sub)) at (prev + 1, 13) to (start + 0, 30)
= (c0 - Zero)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
- Code(Counter(9)) at (prev + 0, 30) to (start + 0, 31)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(39, Sub)) at (prev + 2, 13) to (start + 0, 14)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (((Zero + c3) + (Zero + c5)) - c6)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(40, Add)) at (prev + 0, 18) to (start + 0, 23)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= ((Zero + c3) + (Zero + c5))
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(39, Sub)) at (prev + 1, 16) to (start + 0, 21)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (((Zero + c3) + (Zero + c5)) - c6)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
- Code(Zero) at (prev + 0, 22) to (start + 1, 14)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(38, Sub)) at (prev + 2, 20) to (start + 0, 25)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= ((((Zero + c3) + (Zero + c5)) - c6) - Zero)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
- Code(Zero) at (prev + 1, 27) to (start + 0, 31)
- Code(Zero) at (prev + 0, 32) to (start + 0, 34)
coverage: Restrict empty-span expansion to only cover `{` and `}`
2024-11-05 04:59:10 -06:00
- Code(Expression(18, Sub)) at (prev + 1, 17) to (start + 0, 18)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (((((Zero + c3) + (Zero + c5)) - c6) - Zero) - Zero)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(38, Sub)) at (prev + 1, 17) to (start + 0, 34)
= ((((Zero + c3) + (Zero + c5)) - c6) - Zero)
- Code(Expression(37, Sub)) at (prev + 0, 34) to (start + 0, 35)
= (((((Zero + c3) + (Zero + c5)) - c6) - Zero) - c5)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
- Code(Counter(6)) at (prev + 3, 9) to (start + 0, 15)
coverage: Simplify counter expressions using simple algebra 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-05-13 22:51:24 -05:00
- Code(Expression(35, Add)) at (prev + 1, 5) to (start + 0, 6)
= (((((((Zero + c3) + (Zero + c5)) - c6) - Zero) - c5) + c6) + c9)
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: c9
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
Function name: loops_branches::main
Raw bytes (9): 0x[01, 01, 00, 01, 01, 37, 01, 05, 02]
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
- Code(Counter(0)) at (prev + 55, 1) to (start + 5, 2)
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: c0
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 06:29:41 -05:00
Reference in New Issue Copy Permalink