nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2025-05-14 02:49:40 +00:00
Code Issues Packages Projects Releases Wiki Activity
master
rust/tests/coverage/let_else_loop.cov-map

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

37 lines
1.5 KiB
Plaintext
Raw Permalink Normal View History

coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Function name: let_else_loop::_if (unused)
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 07:52:55 +00:00
Raw bytes (24): 0x[01, 01, 00, 04, 00, 16, 01, 00, 13, 00, 01, 08, 00, 0c, 00, 00, 0f, 00, 16, 00, 00, 20, 00, 27]
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Number of files: 1
coverage-dump: Dump filenames instead of global file IDs (and bless)
2025-04-24 07:36:50 +00:00
- file 0 => $DIR/let_else_loop.rs
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Number of expressions: 0
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 07:52:55 +00:00
Number of file 0 mappings: 4
- Code(Zero) at (prev + 22, 1) to (start + 0, 19)
- Code(Zero) at (prev + 1, 8) to (start + 0, 12)
- Code(Zero) at (prev + 0, 15) to (start + 0, 22)
Manually run `x fmt` on all source files in `tests/coverage/` Currently we can't automatically enforce formatting on tests (see #125637), but we can at least keep things relatively tidy by occasionally running the formatter manually. This was done by temporarily commenting out the `"/tests/"` exclusion in `rustfmt.toml`, and then running `x fmt tests/coverage` and `x test coverage --bless`.
2024-05-29 04:27:57 +00:00
- Code(Zero) at (prev + 0, 32) to (start + 0, 39)
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: (none)
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Function name: let_else_loop::_loop_either_way (unused)
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 07:52:55 +00:00
Raw bytes (24): 0x[01, 01, 00, 04, 00, 0f, 01, 00, 20, 00, 01, 10, 00, 14, 00, 00, 1c, 00, 23, 00, 01, 05, 00, 0c]
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Number of files: 1
coverage-dump: Dump filenames instead of global file IDs (and bless)
2025-04-24 07:36:50 +00:00
- file 0 => $DIR/let_else_loop.rs
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Number of expressions: 0
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 07:52:55 +00:00
Number of file 0 mappings: 4
- Code(Zero) at (prev + 15, 1) to (start + 0, 32)
- Code(Zero) at (prev + 1, 16) to (start + 0, 20)
- Code(Zero) at (prev + 0, 28) to (start + 0, 35)
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
- Code(Zero) at (prev + 1, 5) to (start + 0, 12)
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: (none)
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Function name: let_else_loop::loopy
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 07:52:55 +00:00
Raw bytes (24): 0x[01, 01, 00, 04, 01, 09, 01, 00, 15, 01, 01, 10, 00, 14, 09, 00, 1c, 00, 23, 05, 01, 01, 00, 02]
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Number of files: 1
coverage-dump: Dump filenames instead of global file IDs (and bless)
2025-04-24 07:36:50 +00:00
- file 0 => $DIR/let_else_loop.rs
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Number of expressions: 0
coverage: Only merge adjacent coverage spans This also removes some manipulation of the function signature span that only made sense in the context of merging non-adjacent spans.
2025-04-12 07:52:55 +00:00
Number of file 0 mappings: 4
- Code(Counter(0)) at (prev + 9, 1) to (start + 0, 21)
- Code(Counter(0)) at (prev + 1, 16) to (start + 0, 20)
- Code(Counter(2)) at (prev + 0, 28) to (start + 0, 35)
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
- Code(Counter(1)) at (prev + 1, 1) to (start + 0, 2)
coverage: Use a query to identify which counter/expression IDs are used
2024-11-24 07:26:05 +00:00
Highest counter ID seen: c2
coverage: Regression test for ICE triggered by self-loops
2024-03-20 07:00:12 +00:00
Reference in New Issue Copy Permalink