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

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

25 lines
794 B
Plaintext
Raw Normal View History

coverage: Regression test for functions with unreachable bodies
2023-09-28 00:08:11 -05:00
Function name: unreachable::UNREACHABLE_CLOSURE::{closure#0}
coverage: Skip spans that can't be un-expanded back to the function body When we extract coverage spans from MIR, we try to "un-expand" them back to spans that are inside the function's body span. In cases where that doesn't succeed, the current code just swaps in the entire body span instead. But that tends to result in coverage spans that are completely unrelated to the control flow of the affected code, so it's better to just discard those spans.
2023-11-26 05:20:16 -06:00
Raw bytes (9): 0x[01, 01, 00, 01, 01, 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
coverage: Skip spans that can't be un-expanded back to the function body When we extract coverage spans from MIR, we try to "un-expand" them back to spans that are inside the function's body span. In cases where that doesn't succeed, the current code just swaps in the entire body span instead. But that tends to result in coverage spans that are completely unrelated to the control flow of the affected code, so it's better to just discard those spans.
2023-11-26 05:20:16 -06:00
- Code(Counter(0)) at (prev + 15, 39) to (start + 0, 71)
coverage: Regression test for functions with unreachable bodies
2023-09-28 00:08:11 -05:00
Function name: unreachable::unreachable_function
coverage: Skip spans that can't be un-expanded back to the function body When we extract coverage spans from MIR, we try to "un-expand" them back to spans that are inside the function's body span. In cases where that doesn't succeed, the current code just swaps in the entire body span instead. But that tends to result in coverage spans that are completely unrelated to the control flow of the affected code, so it's better to just discard those spans.
2023-11-26 05:20:16 -06:00
Raw bytes (9): 0x[01, 01, 00, 01, 01, 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
coverage: Skip spans that can't be un-expanded back to the function body When we extract coverage spans from MIR, we try to "un-expand" them back to spans that are inside the function's body span. In cases where that doesn't succeed, the current code just swaps in the entire body span instead. But that tends to result in coverage spans that are completely unrelated to the control flow of the affected code, so it's better to just discard those spans.
2023-11-26 05:20:16 -06:00
- Code(Counter(0)) at (prev + 17, 1) to (start + 1, 37)
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: Regression test for functions with unreachable bodies
2023-09-28 00:08:11 -05:00
Reference in New Issue Copy Permalink