diff options
| author | Zalathar <Zalathar@users.noreply.github.com> | 2024-02-15 18:12:27 +1100 |
|---|---|---|
| committer | Zalathar <Zalathar@users.noreply.github.com> | 2024-02-16 10:57:03 +1100 |
| commit | cd9021e8cb1ab6cf5bdf341d7e0538703d86fc5b (patch) | |
| tree | 8b35a966f14498003af9fdee4b3ae6fa5b92441e /tests/coverage/inline-dead.cov-map | |
| parent | 75af3c58f9df479894465e81d374e047082e8789 (diff) | |
| download | rust-cd9021e8cb1ab6cf5bdf341d7e0538703d86fc5b.tar.gz rust-cd9021e8cb1ab6cf5bdf341d7e0538703d86fc5b.zip | |
coverage: Discard spans that fill the entire function body
When we try to extract coverage-relevant spans from MIR, sometimes we see MIR statements/terminators whose spans cover the entire function body. Those spans tend to be unhelpful for coverage purposes, because they often represent compiler-inserted code, e.g. the implicit return value of `()`.
Diffstat (limited to 'tests/coverage/inline-dead.cov-map')
| -rw-r--r-- | tests/coverage/inline-dead.cov-map | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/tests/coverage/inline-dead.cov-map b/tests/coverage/inline-dead.cov-map index c669b7245ea..f77781ca028 100644 --- a/tests/coverage/inline-dead.cov-map +++ b/tests/coverage/inline-dead.cov-map @@ -22,13 +22,13 @@ Number of file 0 mappings: 4 = (Zero + (c0 - Zero)) Function name: inline_dead::main -Raw bytes (14): 0x[01, 01, 00, 02, 01, 04, 01, 03, 0d, 01, 05, 06, 02, 02] +Raw bytes (14): 0x[01, 01, 00, 02, 01, 04, 01, 03, 0a, 01, 06, 05, 01, 02] Number of files: 1 - file 0 => global file 1 Number of expressions: 0 Number of file 0 mappings: 2 -- Code(Counter(0)) at (prev + 4, 1) to (start + 3, 13) -- Code(Counter(0)) at (prev + 5, 6) to (start + 2, 2) +- Code(Counter(0)) at (prev + 4, 1) to (start + 3, 10) +- Code(Counter(0)) at (prev + 6, 5) to (start + 1, 2) Function name: inline_dead::main::{closure#0} Raw bytes (23): 0x[01, 01, 02, 00, 06, 01, 00, 03, 01, 07, 17, 01, 16, 00, 01, 17, 00, 18, 03, 01, 05, 00, 06] |