mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
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.

52 lines
2.0 KiB
Plaintext
Raw Permalink Normal View History

coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Function name: fn_sig_into_try::a
coverage: Tweak individual tests to be unaffected by `rustfmt` Some of these tests use non-standard formatting that we can simulate by strategically adding `//` line comments. One contains `where` clauses that would be split across multiple lines, which we can keep on one line by moving the bounds to the generic type instead.
2024-01-15 21:12:10 -06:00
Raw bytes (9): 0x[01, 01, 00, 01, 01, 0a, 01, 05, 02]
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
coverage: Tweak individual tests to be unaffected by `rustfmt` Some of these tests use non-standard formatting that we can simulate by strategically adding `//` line comments. One contains `where` clauses that would be split across multiple lines, which we can keep on one line by moving the bounds to the generic type instead.
2024-01-15 21:12:10 -06:00
- Code(Counter(0)) at (prev + 10, 1) to (start + 5, 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-07 21:13:05 -05:00
Highest counter ID seen: c0
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Function name: fn_sig_into_try::b
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-13 22:51:24 -05:00
Raw bytes (26): 0x[01, 01, 01, 01, 00, 04, 01, 11, 01, 03, 0f, 00, 03, 0f, 00, 10, 02, 01, 05, 00, 0c, 01, 01, 01, 00, 02]
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Number of files: 1
- file 0 => global file 1
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-13 22:51:24 -05:00
Number of expressions: 1
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
- expression 0 operands: lhs = Counter(0), rhs = Zero
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Number of file 0 mappings: 4
coverage: Tweak individual tests to be unaffected by `rustfmt` Some of these tests use non-standard formatting that we can simulate by strategically adding `//` line comments. One contains `where` clauses that would be split across multiple lines, which we can keep on one line by moving the bounds to the generic type instead.
2024-01-15 21:12:10 -06:00
- Code(Counter(0)) at (prev + 17, 1) to (start + 3, 15)
- Code(Zero) at (prev + 3, 15) to (start + 0, 16)
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
- Code(Expression(0, Sub)) at (prev + 1, 5) to (start + 0, 12)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (c0 - Zero)
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-13 22:51:24 -05: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-07 21:13:05 -05:00
Highest counter ID seen: c0
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Function name: fn_sig_into_try::c
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-13 22:51:24 -05:00
Raw bytes (26): 0x[01, 01, 01, 01, 00, 04, 01, 18, 01, 03, 17, 00, 03, 17, 00, 18, 02, 01, 05, 00, 0c, 01, 01, 01, 00, 02]
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Number of files: 1
- file 0 => global file 1
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-13 22:51:24 -05:00
Number of expressions: 1
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
- expression 0 operands: lhs = Counter(0), rhs = Zero
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Number of file 0 mappings: 4
coverage: Tweak individual tests to be unaffected by `rustfmt` Some of these tests use non-standard formatting that we can simulate by strategically adding `//` line comments. One contains `where` clauses that would be split across multiple lines, which we can keep on one line by moving the bounds to the generic type instead.
2024-01-15 21:12:10 -06:00
- Code(Counter(0)) at (prev + 24, 1) to (start + 3, 23)
- Code(Zero) at (prev + 3, 23) to (start + 0, 24)
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
- Code(Expression(0, Sub)) at (prev + 1, 5) to (start + 0, 12)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (c0 - Zero)
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-13 22:51:24 -05: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-07 21:13:05 -05:00
Highest counter ID seen: c0
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Function name: fn_sig_into_try::d
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-13 22:51:24 -05:00
Raw bytes (26): 0x[01, 01, 01, 01, 00, 04, 01, 1f, 01, 04, 0f, 00, 04, 0f, 00, 10, 02, 01, 05, 00, 0c, 01, 01, 01, 00, 02]
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Number of files: 1
- file 0 => global file 1
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-13 22:51:24 -05:00
Number of expressions: 1
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
- expression 0 operands: lhs = Counter(0), rhs = Zero
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Number of file 0 mappings: 4
coverage: Tweak individual tests to be unaffected by `rustfmt` Some of these tests use non-standard formatting that we can simulate by strategically adding `//` line comments. One contains `where` clauses that would be split across multiple lines, which we can keep on one line by moving the bounds to the generic type instead.
2024-01-15 21:12:10 -06:00
- Code(Counter(0)) at (prev + 31, 1) to (start + 4, 15)
- Code(Zero) at (prev + 4, 15) to (start + 0, 16)
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
- Code(Expression(0, Sub)) at (prev + 1, 5) to (start + 0, 12)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (c0 - Zero)
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-13 22:51:24 -05: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-07 21:13:05 -05:00
Highest counter ID seen: c0
coverage: Add a test showing the inconsistent handling of function signatures
2023-10-17 02:41:10 -05:00
Reference in New Issue Copy Permalink