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

28 lines
896 B
Plaintext
Raw Permalink Normal View History

Eliminate `UbCheck` for non-standard libraries
2024-03-10 03:29:39 -05:00
Function name: unreachable::UNREACHABLE_CLOSURE::{closure#0} (unused)
Raw bytes (9): 0x[01, 01, 00, 01, 00, 0f, 27, 00, 47]
coverage: Regression test for functions with unreachable bodies
2023-09-28 00:08:11 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
Eliminate `UbCheck` for non-standard libraries
2024-03-10 03:29:39 -05:00
- Code(Zero) at (prev + 15, 39) to (start + 0, 71)
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: (none)
coverage: Regression test for functions with unreachable bodies
2023-09-28 00:08:11 -05:00
Eliminate `UbCheck` for non-standard libraries
2024-03-10 03:29:39 -05:00
Function name: unreachable::unreachable_function (unused)
Raw bytes (9): 0x[01, 01, 00, 01, 00, 11, 01, 01, 25]
coverage: Regression test for functions with unreachable bodies
2023-09-28 00:08:11 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
Eliminate `UbCheck` for non-standard libraries
2024-03-10 03:29:39 -05:00
- Code(Zero) at (prev + 17, 1) to (start + 1, 37)
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: (none)
coverage: Regression test for functions with unreachable bodies
2023-09-28 00:08:11 -05:00
coverage: Re-enable `UnreachablePropagation` for coverage builds
2024-03-21 21:34:26 -05:00
Function name: unreachable::unreachable_intrinsic (unused)
Raw bytes (9): 0x[01, 01, 00, 01, 00, 16, 01, 01, 2c]
coverage: Regression test for functions with unreachable bodies
2023-09-28 00:08:11 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
coverage: Re-enable `UnreachablePropagation` for coverage builds
2024-03-21 21:34:26 -05:00
- Code(Zero) at (prev + 22, 1) to (start + 1, 44)
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: (none)
coverage: Regression test for functions with unreachable bodies
2023-09-28 00:08:11 -05:00
Reference in New Issue Copy Permalink