rust/tests/coverage/async_block.cov-map

Function name: async_block::main
Raw bytes (36): 0x[01, 01, 01, 01, 05, 06, 01, 08, 01, 00, 0b, 05, 01, 09, 00, 0a, 03, 00, 0e, 00, 13, 05, 00, 14, 01, 16, 05, 07, 0a, 02, 06, 01, 03, 01, 00, 02]
Number of files: 1
- file 0 => global file 1
Number of expressions: 1
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
Number of file 0 mappings: 6
- Code(Counter(0)) at (prev + 8, 1) to (start + 0, 11)
- Code(Counter(1)) at (prev + 1, 9) to (start + 0, 10)
- Code(Expression(0, Add)) at (prev + 0, 14) to (start + 0, 19)
    = (c0 + c1)
- Code(Counter(1)) at (prev + 0, 20) to (start + 1, 22)
- Code(Counter(1)) at (prev + 7, 10) to (start + 2, 6)
- Code(Counter(0)) at (prev + 3, 1) to (start + 0, 2)
Highest counter ID seen: c1

Function name: async_block::main::{closure#0}
Raw bytes (26): 0x[01, 01, 01, 01, 05, 04, 01, 0a, 1c, 01, 17, 05, 01, 18, 02, 0e, 02, 02, 14, 02, 0e, 01, 03, 09, 00, 0a]
Number of files: 1
- file 0 => global file 1
Number of expressions: 1
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
Number of file 0 mappings: 4
- Code(Counter(0)) at (prev + 10, 28) to (start + 1, 23)
- Code(Counter(1)) at (prev + 1, 24) to (start + 2, 14)
- Code(Expression(0, Sub)) at (prev + 2, 20) to (start + 2, 14)
    = (c0 - c1)
- Code(Counter(0)) at (prev + 3, 9) to (start + 0, 10)
Highest counter ID seen: c1
coverage: Add a test for `async` blocks We have coverage tests that use async functions, but none that use async blocks. 2023-12-19 05:17:10 -06:00			`Function name: async_block::main`
coverage: Extract `executor::block_on` from several async coverage tests By moving `block_on` to an auxiliary crate, we avoid having to keep a separate copy of it in every async test. (This also incorporates some small tweaks to the headers in `await_ready.rs`.) 2024-09-06 00:41:10 -05:00			`Raw bytes (36): 0x[01, 01, 01, 01, 05, 06, 01, 08, 01, 00, 0b, 05, 01, 09, 00, 0a, 03, 00, 0e, 00, 13, 05, 00, 14, 01, 16, 05, 07, 0a, 02, 06, 01, 03, 01, 00, 02]`
coverage: Add a test for `async` blocks We have coverage tests that use async functions, but none that use async blocks. 2023-12-19 05:17:10 -06: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: 1`
coverage: Add a test for `async` blocks We have coverage tests that use async functions, but none that use async blocks. 2023-12-19 05:17:10 -06:00			`- expression 0 operands: lhs = Counter(0), rhs = Counter(1)`
			`Number of file 0 mappings: 6`
coverage: Extract `executor::block_on` from several async coverage tests By moving `block_on` to an auxiliary crate, we avoid having to keep a separate copy of it in every async test. (This also incorporates some small tweaks to the headers in `await_ready.rs`.) 2024-09-06 00:41:10 -05:00			`- Code(Counter(0)) at (prev + 8, 1) to (start + 0, 11)`
coverage: Add a test for `async` blocks We have coverage tests that use async functions, but none that use async blocks. 2023-12-19 05:17:10 -06:00			`- Code(Counter(1)) at (prev + 1, 9) to (start + 0, 10)`
			`- Code(Expression(0, Add)) at (prev + 0, 14) to (start + 0, 19)`
			`= (c0 + c1)`
			`- Code(Counter(1)) at (prev + 0, 20) to (start + 1, 22)`
			`- Code(Counter(1)) at (prev + 7, 10) to (start + 2, 6)`
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(0)) at (prev + 3, 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-07 21:13:05 -05:00			`Highest counter ID seen: c1`
coverage: Add a test for `async` blocks We have coverage tests that use async functions, but none that use async blocks. 2023-12-19 05:17:10 -06:00
			`Function name: async_block::main::{closure#0}`
coverage: Extract `executor::block_on` from several async coverage tests By moving `block_on` to an auxiliary crate, we avoid having to keep a separate copy of it in every async test. (This also incorporates some small tweaks to the headers in `await_ready.rs`.) 2024-09-06 00:41:10 -05:00			`Raw bytes (26): 0x[01, 01, 01, 01, 05, 04, 01, 0a, 1c, 01, 17, 05, 01, 18, 02, 0e, 02, 02, 14, 02, 0e, 01, 03, 09, 00, 0a]`
coverage: Add a test for `async` blocks We have coverage tests that use async functions, but none that use async blocks. 2023-12-19 05:17:10 -06: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: 1`
coverage: Add a test for `async` blocks We have coverage tests that use async functions, but none that use async blocks. 2023-12-19 05:17:10 -06:00			`- expression 0 operands: lhs = Counter(0), rhs = Counter(1)`
			`Number of file 0 mappings: 4`
coverage: Extract `executor::block_on` from several async coverage tests By moving `block_on` to an auxiliary crate, we avoid having to keep a separate copy of it in every async test. (This also incorporates some small tweaks to the headers in `await_ready.rs`.) 2024-09-06 00:41:10 -05:00			`- Code(Counter(0)) at (prev + 10, 28) to (start + 1, 23)`
coverage: Add a test for `async` blocks We have coverage tests that use async functions, but none that use async blocks. 2023-12-19 05:17:10 -06:00			`- Code(Counter(1)) at (prev + 1, 24) to (start + 2, 14)`
			`- Code(Expression(0, Sub)) at (prev + 2, 20) to (start + 2, 14)`
			`= (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-13 22:51:24 -05:00			`- Code(Counter(0)) at (prev + 3, 9) to (start + 0, 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-07 21:13:05 -05:00			`Highest counter ID seen: c1`
coverage: Add a test for `async` blocks We have coverage tests that use async functions, but none that use async blocks. 2023-12-19 05:17:10 -06:00