rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
359bfa901b9d8eddbed7b88b6716dbb77b7bfb95
rust/tests/coverage/simple_match.cov-map

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

35 lines
1.9 KiB
Plaintext
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: simple_match::main
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 17:52:55 +10:00
Raw bytes (99): 0x[01, 01, 05, 01, 05, 09, 01, 09, 01, 09, 13, 01, 0d, 11, 01, 04, 01, 00, 0a, 01, 04, 09, 00, 10, 01, 00, 13, 00, 2e, 01, 02, 09, 00, 16, 01, 00, 19, 00, 1a, 01, 01, 08, 00, 0f, 05, 00, 10, 02, 06, 02, 02, 05, 00, 06, 09, 05, 09, 00, 0d, 0a, 05, 0d, 00, 16, 0d, 02, 0d, 00, 0e, 0a, 02, 11, 02, 12, 0d, 04, 0d, 07, 0e, 0d, 01, 11, 00, 1e, 0d, 02, 15, 00, 16, 0e, 07, 0d, 00, 0f, 01, 03, 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
coverage-dump: Dump filenames instead of global file IDs (and bless)
2025-04-24 17:36:50 +10:00
- file 0 => $DIR/simple_match.rs
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
Number of expressions: 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 21:29:41 +10:00
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
- expression 1 operands: lhs = Counter(2), rhs = Counter(0)
- expression 2 operands: lhs = Counter(2), rhs = Counter(0)
- expression 3 operands: lhs = Counter(2), rhs = Expression(4, Add)
- expression 4 operands: lhs = Counter(0), rhs = Counter(3)
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 17:52:55 +10:00
Number of file 0 mappings: 17
- Code(Counter(0)) at (prev + 4, 1) to (start + 0, 10)
- Code(Counter(0)) at (prev + 4, 9) to (start + 0, 16)
- Code(Counter(0)) at (prev + 0, 19) to (start + 0, 46)
- Code(Counter(0)) at (prev + 2, 9) to (start + 0, 22)
- Code(Counter(0)) at (prev + 0, 25) to (start + 0, 26)
- Code(Counter(0)) at (prev + 1, 8) to (start + 0, 15)
- Code(Counter(1)) at (prev + 0, 16) to (start + 2, 6)
coverage: Restrict empty-span expansion to only cover `{` and `}`
2024-11-05 21:59:10 +11:00
- Code(Expression(0, Sub)) at (prev + 2, 5) to (start + 0, 6)
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
= (c0 - c1)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
- Code(Counter(2)) at (prev + 5, 9) to (start + 0, 13)
- Code(Expression(2, Sub)) at (prev + 5, 13) to (start + 0, 22)
= (c2 - c0)
- Code(Counter(3)) at (prev + 2, 13) to (start + 0, 14)
- Code(Expression(2, Sub)) at (prev + 2, 17) to (start + 2, 18)
= (c2 - c0)
- Code(Counter(3)) at (prev + 4, 13) to (start + 7, 14)
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 17:52:55 +10:00
- Code(Counter(3)) at (prev + 1, 17) to (start + 0, 30)
- Code(Counter(3)) at (prev + 2, 21) to (start + 0, 22)
- Code(Expression(3, Sub)) at (prev + 7, 13) to (start + 0, 15)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c2 - (c0 + c3))
- Code(Counter(0)) at (prev + 3, 1) to (start + 0, 2)
Highest counter ID seen: c3
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 New Issue Copy Permalink