rust/tests/coverage/assert_not.cov-map

Function name: assert_not::main
Raw bytes (29): 0x[01, 01, 00, 05, 01, 06, 01, 01, 12, 05, 02, 05, 00, 14, 09, 01, 05, 00, 14, 0d, 01, 05, 00, 16, 0d, 01, 01, 00, 02]
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 5
- Code(Counter(0)) at (prev + 6, 1) to (start + 1, 18)
- Code(Counter(1)) at (prev + 2, 5) to (start + 0, 20)
- Code(Counter(2)) at (prev + 1, 5) to (start + 0, 20)
- Code(Counter(3)) at (prev + 1, 5) to (start + 0, 22)
- Code(Counter(3)) at (prev + 1, 1) to (start + 0, 2)
Highest counter ID seen: c3
coverage: Regression test for `assert!(!false)` 2023-12-16 09:57:20 +00:00			`Function name: assert_not::main`
coverage: Don't create counters for code that was removed by MIR opts 2025-01-25 07:24:02 +00:00			`Raw bytes (29): 0x[01, 01, 00, 05, 01, 06, 01, 01, 12, 05, 02, 05, 00, 14, 09, 01, 05, 00, 14, 0d, 01, 05, 00, 16, 0d, 01, 01, 00, 02]`
coverage: Regression test for `assert!(!false)` 2023-12-16 09:57:20 +00:00			`Number of files: 1`
			`- file 0 => global file 1`
coverage: Don't create counters for code that was removed by MIR opts 2025-01-25 07:24:02 +00:00			`Number of expressions: 0`
coverage: Regression test for `assert!(!false)` 2023-12-16 09:57:20 +00:00			`Number of file 0 mappings: 5`
			`- Code(Counter(0)) at (prev + 6, 1) to (start + 1, 18)`
			`- Code(Counter(1)) at (prev + 2, 5) to (start + 0, 20)`
coverage: Completely overhaul counter assignment, using node-flow graphs 2025-01-12 10:36:07 +00:00			`- Code(Counter(2)) at (prev + 1, 5) to (start + 0, 20)`
coverage: Regression test for `assert!(!false)` 2023-12-16 09:57:20 +00:00			`- Code(Counter(3)) at (prev + 1, 5) to (start + 0, 22)`
coverage: Don't create counters for code that was removed by MIR opts 2025-01-25 07:24:02 +00:00			`- Code(Counter(3)) 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 02:13:05 +00:00			`Highest counter ID seen: c3`
coverage: Regression test for `assert!(!false)` 2023-12-16 09:57:20 +00:00