mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
master
rust/tests/coverage/bad_counter_ids.cov-map

91 lines
3.3 KiB
Plaintext
Raw Permalink Normal View History

coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Function name: bad_counter_ids::eq_bad
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
Raw bytes (14): 0x[01, 01, 00, 02, 01, 24, 01, 02, 1f, 00, 03, 01, 00, 02]
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 2
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
- Code(Counter(0)) at (prev + 36, 1) to (start + 2, 31)
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
- Code(Zero) at (prev + 3, 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: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Function name: bad_counter_ids::eq_bad_message
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
Raw bytes (21): 0x[01, 01, 01, 01, 00, 03, 01, 29, 01, 02, 0f, 02, 02, 20, 00, 2b, 00, 01, 01, 00, 02]
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of files: 1
- file 0 => global file 1
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: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of file 0 mappings: 3
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
- Code(Counter(0)) at (prev + 41, 1) to (start + 2, 15)
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
- Code(Expression(0, Sub)) at (prev + 2, 32) to (start + 0, 43)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (c0 - Zero)
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
- Code(Zero) 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: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Function name: bad_counter_ids::eq_good
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
Raw bytes (14): 0x[01, 01, 00, 02, 01, 10, 01, 02, 1f, 05, 03, 01, 00, 02]
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 2
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
- Code(Counter(0)) at (prev + 16, 1) to (start + 2, 31)
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
- Code(Counter(1)) at (prev + 3, 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: c1
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Function name: bad_counter_ids::eq_good_message
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
Raw bytes (19): 0x[01, 01, 00, 03, 01, 15, 01, 02, 0f, 00, 02, 20, 00, 2b, 05, 01, 01, 00, 02]
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 3
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
- Code(Counter(0)) at (prev + 21, 1) to (start + 2, 15)
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
- Code(Zero) at (prev + 2, 32) to (start + 0, 43)
- Code(Counter(1)) 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: c1
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Function name: bad_counter_ids::ne_bad
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
Raw bytes (14): 0x[01, 01, 00, 02, 01, 2e, 01, 02, 1f, 00, 03, 01, 00, 02]
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 2
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
- Code(Counter(0)) at (prev + 46, 1) to (start + 2, 31)
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
- Code(Zero) at (prev + 3, 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: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Function name: bad_counter_ids::ne_bad_message
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
Raw bytes (19): 0x[01, 01, 00, 03, 01, 33, 01, 02, 0f, 05, 02, 20, 00, 2b, 00, 01, 01, 00, 02]
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of files: 1
- file 0 => global file 1
Number of expressions: 0
Number of file 0 mappings: 3
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
- Code(Counter(0)) at (prev + 51, 1) to (start + 2, 15)
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
- Code(Counter(1)) at (prev + 2, 32) to (start + 0, 43)
- Code(Zero) 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: c1
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Function name: bad_counter_ids::ne_good
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
Raw bytes (16): 0x[01, 01, 01, 01, 00, 02, 01, 1a, 01, 02, 1f, 02, 03, 01, 00, 02]
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of files: 1
- file 0 => global file 1
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: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of file 0 mappings: 2
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
- Code(Counter(0)) at (prev + 26, 1) to (start + 2, 31)
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
- Code(Expression(0, Sub)) at (prev + 3, 1) to (start + 0, 2)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (c0 - Zero)
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: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Function name: bad_counter_ids::ne_good_message
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
Raw bytes (21): 0x[01, 01, 01, 01, 00, 03, 01, 1f, 01, 02, 0f, 00, 02, 20, 00, 2b, 02, 01, 01, 00, 02]
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of files: 1
- file 0 => global file 1
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: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Number of file 0 mappings: 3
coverage: Use normal `edition:` headers in coverage tests Some of these tests were originally written as part of a custom `run-make` test, so at that time they weren't able to use the normal compiletest header directive parser. Now that they're properly integrated, there's no need for them to use `compile-flags` to specify the edition, since they can use `edition` instead.
2024-01-12 00:12:45 -06:00
- Code(Counter(0)) at (prev + 31, 1) to (start + 2, 15)
coverage: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
- Code(Zero) at (prev + 2, 32) to (start + 0, 43)
- Code(Expression(0, Sub)) at (prev + 1, 1) to (start + 0, 2)
coverage: Consistently remove unused counter IDs from expressions/mappings
2023-10-24 06:48:59 -05:00
= (c0 - Zero)
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: Regression test for #17012 (bad counter IDs in mappings)
2023-10-20 05:12:24 -05:00
Reference in New Issue Copy Permalink