bjoernager/rust
bjoernager/rust
1
Fork 0
Code Issues Pull requests Activity
rust/tests/coverage/issue-84561.cov-map

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

207 lines
12 KiB
Text
Raw 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 21:29:41 +10:00
Function name: <issue_84561::Foo as core::fmt::Debug>::fmt
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-14 13:51:24 +10:00
Raw bytes (27): 0x[01, 01, 01, 01, 05, 04, 01, 8a, 01, 05, 01, 25, 05, 01, 25, 00, 26, 02, 01, 09, 00, 0f, 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 21:29:41 +10: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-14 13:51:24 +10:00
Number of expressions: 1
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 21:29:41 +10:00
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
Number of file 0 mappings: 4
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
- Code(Counter(0)) at (prev + 138, 5) to (start + 1, 37)
coverage: Handle fn signature spans more consistently near `?`
2023-10-17 18:58:35 +11:00
- Code(Counter(1)) at (prev + 1, 37) to (start + 0, 38)
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 21:29:41 +10:00
- Code(Expression(0, Sub)) at (prev + 1, 9) to (start + 0, 15)
= (c0 - c1)
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-14 13:51:24 +10:00
- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 6)
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-08 13:13:05 +11:00
Highest counter ID seen: c1
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 21:29:41 +10:00
Function name: issue_84561::main
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
Raw bytes (10): 0x[01, 01, 00, 01, 01, b4, 01, 01, 04, 02]
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 21:29:41 +10:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
- Code(Counter(0)) at (prev + 180, 1) to (start + 4, 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-08 13:13:05 +11: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 21:29:41 +10:00
Function name: issue_84561::test1
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-14 13:51:24 +10:00
Raw bytes (50): 0x[01, 01, 00, 09, 01, 9a, 01, 01, 01, 0b, 05, 01, 0c, 00, 1e, 01, 01, 05, 00, 0b, 09, 00, 0c, 00, 1e, 01, 01, 0d, 01, 0b, 0d, 01, 0c, 00, 1e, 01, 01, 05, 03, 0b, 11, 03, 0c, 00, 1e, 01, 01, 01, 00, 02]
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 21:29:41 +10: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-14 13:51:24 +10:00
Number of expressions: 0
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 21:29:41 +10:00
Number of file 0 mappings: 9
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
- Code(Counter(0)) at (prev + 154, 1) to (start + 1, 11)
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 21:29:41 +10:00
- Code(Counter(1)) at (prev + 1, 12) to (start + 0, 30)
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-14 13:51:24 +10:00
- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 11)
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 21:29:41 +10:00
- Code(Counter(2)) at (prev + 0, 12) to (start + 0, 30)
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-14 13:51:24 +10:00
- Code(Counter(0)) at (prev + 1, 13) to (start + 1, 11)
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 21:29:41 +10:00
- Code(Counter(3)) at (prev + 1, 12) to (start + 0, 30)
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-14 13:51:24 +10:00
- Code(Counter(0)) at (prev + 1, 5) to (start + 3, 11)
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 21:29:41 +10:00
- Code(Counter(4)) at (prev + 3, 12) to (start + 0, 30)
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-14 13:51:24 +10:00
- Code(Counter(0)) at (prev + 1, 1) to (start + 0, 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-08 13:13:05 +11:00
Highest counter ID seen: 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 21:29:41 +10:00
Function name: issue_84561::test2
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-14 13:51:24 +10:00
Raw bytes (20): 0x[01, 01, 00, 03, 01, b0, 01, 01, 01, 10, 05, 01, 11, 00, 23, 01, 01, 01, 00, 02]
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 21:29:41 +10: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-14 13:51:24 +10:00
Number of expressions: 0
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 21:29:41 +10:00
Number of file 0 mappings: 3
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
- Code(Counter(0)) at (prev + 176, 1) to (start + 1, 16)
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 21:29:41 +10:00
- Code(Counter(1)) at (prev + 1, 17) to (start + 0, 35)
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-14 13:51:24 +10:00
- Code(Counter(0)) at (prev + 1, 1) to (start + 0, 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-08 13:13:05 +11:00
Highest counter ID seen: c1
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 21:29:41 +10:00
Function name: issue_84561::test2::call_print
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
Raw bytes (10): 0x[01, 01, 00, 01, 01, a7, 01, 09, 02, 0a]
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 21:29:41 +10:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
- Code(Counter(0)) at (prev + 167, 9) to (start + 2, 10)
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-08 13:13:05 +11: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 21:29:41 +10:00
Function name: issue_84561::test3
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
Raw bytes (409): 0x[01, 01, 3b, 05, 09, 0d, 11, 15, 19, 15, 1f, 19, 1d, 15, 1b, 1f, 21, 19, 1d, 25, 29, 21, 25, 2d, 31, 21, 33, 25, 2d, 35, 39, 3d, 41, 3d, 43, 41, 45, 5f, 4d, 45, 49, 5f, 67, 45, 49, 4d, 51, 5f, 63, 45, 49, 67, 59, 4d, 51, 97, 01, 55, 51, 59, 97, 01, 55, 51, 59, 97, 01, 83, 01, 51, 59, 55, 5d, 97, 01, 9f, 01, 51, 59, 55, 61, 97, 01, 9b, 01, 51, 59, 9f, 01, 65, 55, 61, db, 01, e7, 01, 69, 71, 6d, 75, 69, 6d, 69, 6d, 69, bb, 01, 6d, 00, 69, e7, 01, 6d, 75, db, 01, e3, 01, 69, 71, e7, 01, 79, 6d, 75, db, 01, df, 01, 69, 71, e3, 01, 7d, e7, 01, 79, 6d, 75, 7d, 81, 01, 33, 01, 08, 01, 03, 1c, 05, 04, 09, 01, 1c, 02, 02, 05, 04, 1f, 0d, 05, 05, 00, 1f, 06, 01, 05, 00, 1f, 15, 01, 09, 01, 1c, 0a, 02, 05, 00, 1f, 0e, 01, 05, 00, 0f, 16, 00, 20, 00, 30, 21, 01, 05, 03, 0f, 25, 03, 20, 00, 30, 29, 00, 33, 00, 41, 22, 00, 4b, 00, 5a, 26, 01, 05, 00, 0f, 2d, 05, 09, 03, 10, 31, 05, 0d, 00, 1b, 2a, 02, 0d, 00, 1c, 2e, 04, 09, 05, 06, 35, 06, 05, 03, 06, 36, 04, 05, 03, 06, 3d, 04, 09, 04, 06, 3a, 05, 08, 00, 0f, 45, 01, 09, 03, 0a, 3e, 05, 09, 03, 0a, 46, 05, 08, 00, 0f, 51, 01, 09, 00, 13, 55, 03, 0d, 00, 1d, 4e, 03, 09, 00, 13, 5a, 03, 0d, 00, 1d, 72, 03, 05, 00, 0f, 72, 01, 0c, 00, 13, 5d, 01, 0d, 00, 13, 7a, 02, 0d, 00, 13, 86, 01, 04, 05, 02, 13, 65, 03, 0d, 00, 13, 92, 01, 02, 0d, 00, 13, a2, 01, 03, 05, 00, 0f, 69, 01, 0c, 00, 13, 6d, 01, 0d, 03, 0e, 71, 04, 0d, 00, 13, b2, 01, 02, 0d, 00, 17, b2, 01, 01, 14, 00, 1b, 00, 01, 15, 00, 1b, b6, 01, 02, 15, 00, 1b, be, 01, 04, 0d, 00, 13, 79, 03, 09, 00, 19, c6, 01, 02, 05, 00, 0f, d6, 01, 03, 09, 00, 22, 7d, 02, 05, 00, 0f, ea, 01, 03, 09, 00, 2c, 81, 01, 02, 01, 00, 02]
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 21:29:41 +10:00
Number of files: 1
- file 0 => global file 1
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
Number of expressions: 59
update coverage test
2024-06-26 00:06:27 +02:00
- expression 0 operands: lhs = Counter(1), rhs = Counter(2)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- expression 1 operands: lhs = Counter(3), rhs = Counter(4)
update coverage test
2024-06-26 00:06:27 +02:00
- expression 2 operands: lhs = Counter(5), rhs = Counter(6)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- expression 3 operands: lhs = Counter(5), rhs = Expression(7, Add)
- expression 4 operands: lhs = Counter(6), rhs = Counter(7)
- expression 5 operands: lhs = Counter(5), rhs = Expression(6, Add)
- expression 6 operands: lhs = Expression(7, Add), rhs = Counter(8)
- expression 7 operands: lhs = Counter(6), rhs = Counter(7)
- expression 8 operands: lhs = Counter(9), rhs = Counter(10)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- expression 9 operands: lhs = Counter(8), rhs = Counter(9)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- expression 10 operands: lhs = Counter(11), rhs = Counter(12)
- expression 11 operands: lhs = Counter(8), rhs = Expression(12, Add)
- expression 12 operands: lhs = Counter(9), rhs = Counter(11)
- expression 13 operands: lhs = Counter(13), rhs = Counter(14)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- expression 14 operands: lhs = Counter(15), rhs = Counter(16)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- expression 15 operands: lhs = Counter(15), rhs = Expression(16, Add)
- expression 16 operands: lhs = Counter(16), rhs = Counter(17)
- expression 17 operands: lhs = Expression(23, Add), rhs = Counter(19)
- expression 18 operands: lhs = Counter(17), rhs = Counter(18)
- expression 19 operands: lhs = Expression(23, Add), rhs = Expression(25, Add)
- expression 20 operands: lhs = Counter(17), rhs = Counter(18)
- expression 21 operands: lhs = Counter(19), rhs = Counter(20)
- expression 22 operands: lhs = Expression(23, Add), rhs = Expression(24, Add)
- expression 23 operands: lhs = Counter(17), rhs = Counter(18)
- expression 24 operands: lhs = Expression(25, Add), rhs = Counter(22)
- expression 25 operands: lhs = Counter(19), rhs = Counter(20)
- expression 26 operands: lhs = Expression(37, Add), rhs = Counter(21)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- expression 27 operands: lhs = Counter(20), rhs = Counter(22)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- expression 28 operands: lhs = Expression(37, Add), rhs = Counter(21)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- expression 29 operands: lhs = Counter(20), rhs = Counter(22)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- expression 30 operands: lhs = Expression(37, Add), rhs = Expression(32, Add)
- expression 31 operands: lhs = Counter(20), rhs = Counter(22)
- expression 32 operands: lhs = Counter(21), rhs = Counter(23)
- expression 33 operands: lhs = Expression(37, Add), rhs = Expression(39, Add)
- expression 34 operands: lhs = Counter(20), rhs = Counter(22)
- expression 35 operands: lhs = Counter(21), rhs = Counter(24)
- expression 36 operands: lhs = Expression(37, Add), rhs = Expression(38, Add)
- expression 37 operands: lhs = Counter(20), rhs = Counter(22)
- expression 38 operands: lhs = Expression(39, Add), rhs = Counter(25)
- expression 39 operands: lhs = Counter(21), rhs = Counter(24)
- expression 40 operands: lhs = Expression(54, Add), rhs = Expression(57, Add)
- expression 41 operands: lhs = Counter(26), rhs = Counter(28)
- expression 42 operands: lhs = Counter(27), rhs = Counter(29)
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-14 13:51:24 +10:00
- expression 43 operands: lhs = Counter(26), rhs = Counter(27)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- expression 44 operands: lhs = Counter(26), rhs = Counter(27)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- expression 45 operands: lhs = Counter(26), rhs = Expression(46, Add)
- expression 46 operands: lhs = Counter(27), rhs = Zero
- expression 47 operands: lhs = Counter(26), rhs = Expression(57, Add)
- expression 48 operands: lhs = Counter(27), rhs = Counter(29)
- expression 49 operands: lhs = Expression(54, Add), rhs = Expression(56, Add)
- expression 50 operands: lhs = Counter(26), rhs = Counter(28)
- expression 51 operands: lhs = Expression(57, Add), rhs = Counter(30)
- expression 52 operands: lhs = Counter(27), rhs = Counter(29)
- expression 53 operands: lhs = Expression(54, Add), rhs = Expression(55, Add)
- expression 54 operands: lhs = Counter(26), rhs = Counter(28)
- expression 55 operands: lhs = Expression(56, Add), rhs = Counter(31)
- expression 56 operands: lhs = Expression(57, Add), rhs = Counter(30)
- expression 57 operands: lhs = Counter(27), rhs = Counter(29)
- expression 58 operands: lhs = Counter(31), rhs = Counter(32)
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 21:29:41 +10:00
Number of file 0 mappings: 51
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
- Code(Counter(0)) at (prev + 8, 1) to (start + 3, 28)
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 21:29:41 +10:00
- Code(Counter(1)) at (prev + 4, 9) to (start + 1, 28)
- Code(Expression(0, Sub)) at (prev + 2, 5) to (start + 4, 31)
update coverage test
2024-06-26 00:06:27 +02:00
= (c1 - c2)
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 21:29:41 +10:00
- Code(Counter(3)) at (prev + 5, 5) to (start + 0, 31)
- Code(Expression(1, Sub)) at (prev + 1, 5) to (start + 0, 31)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
= (c3 - 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 21:29:41 +10:00
- Code(Counter(5)) at (prev + 1, 9) to (start + 1, 28)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- Code(Expression(2, Sub)) at (prev + 2, 5) to (start + 0, 31)
update coverage test
2024-06-26 00:06:27 +02:00
= (c5 - c6)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- Code(Expression(3, Sub)) at (prev + 1, 5) to (start + 0, 15)
= (c5 - (c6 + c7))
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(5, Sub)) at (prev + 0, 32) to (start + 0, 48)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= (c5 - ((c6 + c7) + c8))
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 21:29:41 +10:00
- Code(Counter(8)) at (prev + 1, 5) to (start + 3, 15)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Counter(9)) at (prev + 3, 32) to (start + 0, 48)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- Code(Counter(10)) at (prev + 0, 51) to (start + 0, 65)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(8, Sub)) at (prev + 0, 75) to (start + 0, 90)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= (c9 - c10)
- Code(Expression(9, Sub)) at (prev + 1, 5) to (start + 0, 15)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
= (c8 - c9)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- Code(Counter(11)) at (prev + 5, 9) to (start + 3, 16)
- Code(Counter(12)) at (prev + 5, 13) to (start + 0, 27)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(10, Sub)) at (prev + 2, 13) to (start + 0, 28)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= (c11 - c12)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(11, Sub)) at (prev + 4, 9) to (start + 5, 6)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= (c8 - (c9 + c11))
- Code(Counter(13)) at (prev + 6, 5) to (start + 3, 6)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(13, Sub)) at (prev + 4, 5) to (start + 3, 6)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= (c13 - c14)
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 21:29:41 +10:00
- Code(Counter(15)) at (prev + 4, 9) to (start + 4, 6)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- Code(Expression(14, Sub)) at (prev + 5, 8) to (start + 0, 15)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
= (c15 - c16)
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 21:29:41 +10:00
- Code(Counter(17)) at (prev + 1, 9) to (start + 3, 10)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(15, Sub)) at (prev + 5, 9) to (start + 3, 10)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= (c15 - (c16 + c17))
- Code(Expression(17, Sub)) at (prev + 5, 8) to (start + 0, 15)
= ((c17 + c18) - c19)
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 21:29:41 +10:00
- Code(Counter(20)) at (prev + 1, 9) to (start + 0, 19)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- Code(Counter(21)) at (prev + 3, 13) to (start + 0, 29)
- Code(Expression(19, Sub)) at (prev + 3, 9) to (start + 0, 19)
= ((c17 + c18) - (c19 + c20))
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(22, Sub)) at (prev + 3, 13) to (start + 0, 29)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= ((c17 + c18) - ((c19 + c20) + c22))
- Code(Expression(28, Sub)) at (prev + 3, 5) to (start + 0, 15)
= ((c20 + c22) - c21)
- Code(Expression(28, Sub)) at (prev + 1, 12) to (start + 0, 19)
= ((c20 + c22) - c21)
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 21:29:41 +10:00
- Code(Counter(23)) at (prev + 1, 13) to (start + 0, 19)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(30, Sub)) at (prev + 2, 13) to (start + 0, 19)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= ((c20 + c22) - (c21 + c23))
- Code(Expression(33, Sub)) at (prev + 4, 5) to (start + 2, 19)
= ((c20 + c22) - (c21 + c24))
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 21:29:41 +10:00
- Code(Counter(25)) at (prev + 3, 13) to (start + 0, 19)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(36, Sub)) at (prev + 2, 13) to (start + 0, 19)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= ((c20 + c22) - ((c21 + c24) + c25))
- Code(Expression(40, Sub)) at (prev + 3, 5) to (start + 0, 15)
= ((c26 + c28) - (c27 + c29))
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 21:29:41 +10:00
- Code(Counter(26)) at (prev + 1, 12) to (start + 0, 19)
- Code(Counter(27)) at (prev + 1, 13) to (start + 3, 14)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- Code(Counter(28)) at (prev + 4, 13) to (start + 0, 19)
- Code(Expression(44, Sub)) at (prev + 2, 13) to (start + 0, 23)
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-14 13:51:24 +10:00
= (c26 - c27)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
- Code(Expression(44, Sub)) at (prev + 1, 20) to (start + 0, 27)
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 21:29:41 +10:00
= (c26 - c27)
Enable by default.
2023-01-18 17:57:50 +00:00
- Code(Zero) at (prev + 1, 21) to (start + 0, 27)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(45, Sub)) at (prev + 2, 21) to (start + 0, 27)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= (c26 - (c27 + Zero))
- Code(Expression(47, Sub)) at (prev + 4, 13) to (start + 0, 19)
= (c26 - (c27 + c29))
- Code(Counter(30)) at (prev + 3, 9) to (start + 0, 25)
- Code(Expression(49, Sub)) at (prev + 2, 5) to (start + 0, 15)
= ((c26 + c28) - ((c27 + c29) + c30))
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(53, Sub)) at (prev + 3, 9) to (start + 0, 34)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= ((c26 + c28) - (((c27 + c29) + c30) + c31))
- Code(Counter(31)) at (prev + 2, 5) to (start + 0, 15)
comment out the old tests instead of adjusting them
2024-11-25 20:38:57 +01:00
- Code(Expression(58, Sub)) at (prev + 3, 9) to (start + 0, 44)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 12:58:35 +11:00
= (c31 - c32)
- Code(Counter(32)) at (prev + 2, 1) to (start + 0, 2)
Highest counter ID seen: c32
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 21:29:41 +10:00
Reference in a new issue Copy permalink