nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2025-04-30 20:17:50 +00:00
Code Issues Packages Projects Releases Wiki Activity
5a14967f7b
rust/tests/coverage/condition/conditions.cov-map

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

139 lines
6.4 KiB
Plaintext
Raw Normal View History

coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Function name: conditions::assign_3_and_or
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
Raw bytes (65): 0x[01, 01, 05, 01, 05, 05, 09, 01, 09, 01, 13, 09, 0d, 09, 01, 1b, 01, 00, 2f, 01, 01, 09, 00, 0a, 01, 00, 0d, 00, 0e, 20, 05, 02, 00, 0d, 00, 0e, 05, 00, 12, 00, 13, 20, 09, 06, 00, 12, 00, 13, 0a, 00, 17, 00, 18, 20, 0d, 0e, 00, 17, 00, 18, 01, 01, 05, 01, 02]
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Number of files: 1
- file 0 => global file 1
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 01:58:35 +00:00
Number of expressions: 5
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
- expression 1 operands: lhs = Counter(1), rhs = Counter(2)
- expression 2 operands: lhs = Counter(0), rhs = Counter(2)
- expression 3 operands: lhs = Counter(0), rhs = Expression(4, Add)
- expression 4 operands: lhs = Counter(2), rhs = Counter(3)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
Number of file 0 mappings: 9
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
- Code(Counter(0)) at (prev + 27, 1) to (start + 0, 47)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Code(Counter(0)) at (prev + 1, 9) to (start + 0, 10)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
- Code(Counter(0)) at (prev + 0, 13) to (start + 0, 14)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(1), false: Expression(0, Sub) } at (prev + 0, 13) to (start + 0, 14)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
true = c1
false = (c0 - c1)
- Code(Counter(1)) at (prev + 0, 18) to (start + 0, 19)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(2), false: Expression(1, Sub) } at (prev + 0, 18) to (start + 0, 19)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
true = c2
false = (c1 - c2)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Code(Expression(2, Sub)) at (prev + 0, 23) to (start + 0, 24)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 01:58:35 +00:00
= (c0 - c2)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(3), false: Expression(3, Sub) } at (prev + 0, 23) to (start + 0, 24)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
true = c3
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
false = (c0 - (c2 + c3))
- Code(Counter(0)) at (prev + 1, 5) to (start + 1, 2)
Highest counter ID seen: c3
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Function name: conditions::assign_3_or_and
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
Raw bytes (63): 0x[01, 01, 04, 01, 05, 01, 0b, 05, 09, 09, 0d, 09, 01, 16, 01, 00, 2f, 01, 01, 09, 00, 0a, 01, 00, 0d, 00, 0e, 20, 05, 02, 00, 0d, 00, 0e, 02, 00, 12, 00, 13, 20, 09, 06, 00, 12, 00, 13, 09, 00, 17, 00, 18, 20, 0d, 0e, 00, 17, 00, 18, 01, 01, 05, 01, 02]
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Number of files: 1
- file 0 => global file 1
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
Number of expressions: 4
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
- expression 1 operands: lhs = Counter(0), rhs = Expression(2, Add)
coverage: Add an extra "transcribe" step after counter creation
2024-11-29 01:58:35 +00:00
- expression 2 operands: lhs = Counter(1), rhs = Counter(2)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- expression 3 operands: lhs = Counter(2), rhs = Counter(3)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
Number of file 0 mappings: 9
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
- Code(Counter(0)) at (prev + 22, 1) to (start + 0, 47)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Code(Counter(0)) at (prev + 1, 9) to (start + 0, 10)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
- Code(Counter(0)) at (prev + 0, 13) to (start + 0, 14)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(1), false: Expression(0, Sub) } at (prev + 0, 13) to (start + 0, 14)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
true = c1
false = (c0 - c1)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Code(Expression(0, Sub)) at (prev + 0, 18) to (start + 0, 19)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
= (c0 - c1)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(2), false: Expression(1, Sub) } at (prev + 0, 18) to (start + 0, 19)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
true = c2
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
false = (c0 - (c1 + c2))
- Code(Counter(2)) at (prev + 0, 23) to (start + 0, 24)
- Branch { true: Counter(3), false: Expression(3, Sub) } at (prev + 0, 23) to (start + 0, 24)
true = c3
false = (c2 - c3)
- Code(Counter(0)) at (prev + 1, 5) to (start + 1, 2)
Highest counter ID seen: c3
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Function name: conditions::assign_and
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
Raw bytes (47): 0x[01, 01, 02, 01, 05, 05, 09, 07, 01, 0c, 01, 00, 21, 01, 01, 09, 00, 0a, 01, 00, 0d, 00, 0e, 20, 05, 02, 00, 0d, 00, 0e, 05, 00, 12, 00, 13, 20, 09, 06, 00, 12, 00, 13, 01, 01, 05, 01, 02]
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Number of files: 1
- file 0 => global file 1
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
Number of expressions: 2
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
- expression 1 operands: lhs = Counter(1), rhs = Counter(2)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
Number of file 0 mappings: 7
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
- Code(Counter(0)) at (prev + 12, 1) to (start + 0, 33)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Code(Counter(0)) at (prev + 1, 9) to (start + 0, 10)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
- Code(Counter(0)) at (prev + 0, 13) to (start + 0, 14)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(1), false: Expression(0, Sub) } at (prev + 0, 13) to (start + 0, 14)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
true = c1
false = (c0 - c1)
- Code(Counter(1)) at (prev + 0, 18) to (start + 0, 19)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(2), false: Expression(1, Sub) } at (prev + 0, 18) to (start + 0, 19)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
true = c2
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
false = (c1 - c2)
- Code(Counter(0)) at (prev + 1, 5) to (start + 1, 2)
Highest counter ID seen: c2
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Function name: conditions::assign_or
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
Raw bytes (49): 0x[01, 01, 03, 01, 05, 01, 0b, 05, 09, 07, 01, 11, 01, 00, 20, 01, 01, 09, 00, 0a, 01, 00, 0d, 00, 0e, 20, 05, 02, 00, 0d, 00, 0e, 02, 00, 12, 00, 13, 20, 09, 06, 00, 12, 00, 13, 01, 01, 05, 01, 02]
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Number of files: 1
- file 0 => global file 1
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
Number of expressions: 3
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
- expression 1 operands: lhs = Counter(0), rhs = Expression(2, Add)
- expression 2 operands: lhs = Counter(1), rhs = Counter(2)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
Number of file 0 mappings: 7
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
- Code(Counter(0)) at (prev + 17, 1) to (start + 0, 32)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Code(Counter(0)) at (prev + 1, 9) to (start + 0, 10)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
- Code(Counter(0)) at (prev + 0, 13) to (start + 0, 14)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(1), false: Expression(0, Sub) } at (prev + 0, 13) to (start + 0, 14)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
true = c1
false = (c0 - c1)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Code(Expression(0, Sub)) at (prev + 0, 18) to (start + 0, 19)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
= (c0 - c1)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(2), false: Expression(1, Sub) } at (prev + 0, 18) to (start + 0, 19)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
true = c2
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
false = (c0 - (c1 + c2))
- Code(Counter(0)) at (prev + 1, 5) to (start + 1, 2)
Highest counter ID seen: c2
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Function name: conditions::foo
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
Raw bytes (9): 0x[01, 01, 00, 01, 01, 20, 01, 02, 02]
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
- Code(Counter(0)) at (prev + 32, 1) to (start + 2, 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 for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Function name: conditions::func_call
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
Raw bytes (37): 0x[01, 01, 02, 01, 05, 05, 09, 05, 01, 24, 01, 01, 0a, 20, 05, 02, 01, 09, 00, 0a, 05, 00, 0e, 00, 0f, 20, 09, 06, 00, 0e, 00, 0f, 01, 01, 01, 00, 02]
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Number of files: 1
- file 0 => global file 1
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
Number of expressions: 2
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- expression 1 operands: lhs = Counter(1), rhs = Counter(2)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
Number of file 0 mappings: 5
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
- Code(Counter(0)) at (prev + 36, 1) to (start + 1, 10)
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
- Branch { true: Counter(1), false: Expression(0, Sub) } at (prev + 1, 9) to (start + 0, 10)
true = c1
false = (c0 - c1)
- Code(Counter(1)) at (prev + 0, 14) to (start + 0, 15)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
- Branch { true: Counter(2), false: Expression(1, Sub) } at (prev + 0, 14) to (start + 0, 15)
coverage: Instrument the RHS value of lazy logical operators When a lazy logical operator (`&&` or `||`) occurs outside of an `if` condition, it normally doesn't have any associated control-flow branch, so we don't have an existing way to track whether it was true or false. This patch adds special code to handle this case, by inserting extra MIR blocks in a diamond shape after evaluating the RHS. This gives us a place to insert the appropriate marker statements, which can then be given their own counters.
2024-05-01 07:33:33 +00:00
true = c2
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 07:57:17 +00:00
false = (c1 - c2)
- Code(Counter(0)) at (prev + 1, 1) to (start + 0, 2)
Highest counter ID seen: c2
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Function name: conditions::simple_assign
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
Raw bytes (9): 0x[01, 01, 00, 01, 01, 07, 01, 03, 02]
coverage: Add a test for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 1
Stabilize #[coverage] attribute
2024-09-23 23:40:22 +00:00
- Code(Counter(0)) at (prev + 7, 1) to (start + 3, 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 for `-Zcoverage-options=condition`
2024-04-29 15:58:14 +00:00
Reference in New Issue Copy Permalink