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
414482f6a0
rust/tests/coverage/fn_sig_into_try.cov-map

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

54 lines
2.3 KiB
Plaintext
Raw Normal View History

coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +00:00
Function name: fn_sig_into_try::a
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, 0a, 01, 00, 16, 01, 03, 05, 00, 0f, 01, 01, 05, 00, 0c, 01, 01, 01, 00, 02]
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +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/fn_sig_into_try.rs
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +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 + 10, 1) to (start + 0, 22)
- Code(Counter(0)) at (prev + 3, 5) to (start + 0, 15)
- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 12)
- Code(Counter(0)) at (prev + 1, 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-08 02:13:05 +00:00
Highest counter ID seen: c0
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +00:00
Function name: fn_sig_into_try::b
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 (29): 0x[01, 01, 00, 05, 01, 11, 01, 00, 16, 01, 03, 05, 00, 0f, 00, 00, 0f, 00, 10, 01, 01, 05, 00, 0c, 01, 01, 01, 00, 02]
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +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/fn_sig_into_try.rs
coverage: Don't create counters for code that was removed by MIR opts
2025-01-25 07:24:02 +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: 5
- Code(Counter(0)) at (prev + 17, 1) to (start + 0, 22)
- Code(Counter(0)) at (prev + 3, 5) to (start + 0, 15)
- Code(Zero) at (prev + 0, 15) to (start + 0, 16)
coverage: Don't create counters for code that was removed by MIR opts
2025-01-25 07:24:02 +00:00
- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 12)
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-14 03:51:24 +00:00
- Code(Counter(0)) at (prev + 1, 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-08 02:13:05 +00:00
Highest counter ID seen: c0
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +00:00
Function name: fn_sig_into_try::c
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 (29): 0x[01, 01, 00, 05, 01, 18, 01, 00, 16, 01, 03, 0d, 00, 17, 00, 00, 17, 00, 18, 01, 01, 05, 00, 0c, 01, 01, 01, 00, 02]
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +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/fn_sig_into_try.rs
coverage: Don't create counters for code that was removed by MIR opts
2025-01-25 07:24:02 +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: 5
- Code(Counter(0)) at (prev + 24, 1) to (start + 0, 22)
- Code(Counter(0)) at (prev + 3, 13) to (start + 0, 23)
- Code(Zero) at (prev + 0, 23) to (start + 0, 24)
coverage: Don't create counters for code that was removed by MIR opts
2025-01-25 07:24:02 +00:00
- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 12)
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-14 03:51:24 +00:00
- Code(Counter(0)) at (prev + 1, 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-08 02:13:05 +00:00
Highest counter ID seen: c0
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +00:00
Function name: fn_sig_into_try::d
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 (39): 0x[01, 01, 00, 07, 01, 1f, 01, 00, 16, 01, 03, 0c, 00, 0e, 01, 00, 11, 00, 13, 01, 01, 05, 00, 0f, 00, 00, 0f, 00, 10, 01, 01, 05, 00, 0c, 01, 01, 01, 00, 02]
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +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/fn_sig_into_try.rs
coverage: Don't create counters for code that was removed by MIR opts
2025-01-25 07:24:02 +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: 7
- Code(Counter(0)) at (prev + 31, 1) to (start + 0, 22)
- Code(Counter(0)) at (prev + 3, 12) to (start + 0, 14)
- Code(Counter(0)) at (prev + 0, 17) to (start + 0, 19)
- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 15)
- Code(Zero) at (prev + 0, 15) to (start + 0, 16)
coverage: Don't create counters for code that was removed by MIR opts
2025-01-25 07:24:02 +00:00
- Code(Counter(0)) at (prev + 1, 5) to (start + 0, 12)
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-14 03:51:24 +00:00
- Code(Counter(0)) at (prev + 1, 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-08 02:13:05 +00:00
Highest counter ID seen: c0
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 07:41:10 +00:00
Reference in New Issue Copy Permalink