bjoernager/rust
bjoernager/rust
1
Fork 0
Code Issues Pull requests Activity
rust/tests/coverage/try_error_result.cov-map

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

207 lines
12 KiB
Text
Raw Normal View History

Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Function name: <try_error_result::Thing1>::get_thing_2
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 13:51:24 +10:00
Raw bytes (26): 0x[01, 01, 01, 01, 05, 04, 01, 29, 05, 01, 18, 05, 02, 0d, 00, 14, 02, 02, 0d, 00, 1a, 01, 02, 05, 00, 06]
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10: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-14 13:51:24 +10:00
Number of expressions: 1
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
coverage: Store all of a function's mappings in function coverage info Previously, mappings were attached to individual coverage statements in MIR. That necessitated special handling in MIR optimizations to avoid deleting those statements, since otherwise codegen would be unable to reassemble the original list of mappings. With this change, a function's list of mappings is now attached to its MIR body, and survives intact even if individual statements are deleted by optimizations.
2023-09-13 12:51:43 +10:00
Number of file 0 mappings: 4
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
- Code(Counter(0)) at (prev + 41, 5) to (start + 1, 24)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
- Code(Counter(1)) at (prev + 2, 13) to (start + 0, 20)
- Code(Expression(0, Sub)) at (prev + 2, 13) to (start + 0, 26)
= (c0 - c1)
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 13:51:24 +10:00
- Code(Counter(0)) at (prev + 2, 5) to (start + 0, 6)
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 13:13:05 +11:00
Highest counter ID seen: c1
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Function name: <try_error_result::Thing2>::call
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 13:51:24 +10:00
Raw bytes (26): 0x[01, 01, 01, 01, 05, 04, 01, 34, 05, 01, 18, 05, 02, 0d, 00, 14, 02, 02, 0d, 00, 13, 01, 02, 05, 00, 06]
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10: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-14 13:51:24 +10:00
Number of expressions: 1
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
coverage: Store all of a function's mappings in function coverage info Previously, mappings were attached to individual coverage statements in MIR. That necessitated special handling in MIR optimizations to avoid deleting those statements, since otherwise codegen would be unable to reassemble the original list of mappings. With this change, a function's list of mappings is now attached to its MIR body, and survives intact even if individual statements are deleted by optimizations.
2023-09-13 12:51:43 +10:00
Number of file 0 mappings: 4
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
- Code(Counter(0)) at (prev + 52, 5) to (start + 1, 24)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
- Code(Counter(1)) at (prev + 2, 13) to (start + 0, 20)
- Code(Expression(0, Sub)) at (prev + 2, 13) to (start + 0, 19)
= (c0 - c1)
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 13:51:24 +10:00
- Code(Counter(0)) at (prev + 2, 5) to (start + 0, 6)
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 13:13:05 +11:00
Highest counter ID seen: c1
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Function name: try_error_result::call
Tweak various coverage test files for slightly nicer formatting For coverage tests, splitting code across multiple lines often makes the resulting coverage report easier to interpret, so we force rustfmt to retain line breaks by adding dummy line comments with `//`.
2024-05-29 14:06:53 +10:00
Raw bytes (26): 0x[01, 01, 01, 01, 05, 04, 01, 05, 01, 01, 14, 05, 02, 09, 00, 10, 02, 02, 09, 00, 0f, 01, 02, 01, 00, 02]
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10: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-14 13:51:24 +10:00
Number of expressions: 1
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
coverage: Store all of a function's mappings in function coverage info Previously, mappings were attached to individual coverage statements in MIR. That necessitated special handling in MIR optimizations to avoid deleting those statements, since otherwise codegen would be unable to reassemble the original list of mappings. With this change, a function's list of mappings is now attached to its MIR body, and survives intact even if individual statements are deleted by optimizations.
2023-09-13 12:51:43 +10:00
Number of file 0 mappings: 4
Tweak various coverage test files for slightly nicer formatting For coverage tests, splitting code across multiple lines often makes the resulting coverage report easier to interpret, so we force rustfmt to retain line breaks by adding dummy line comments with `//`.
2024-05-29 14:06:53 +10:00
- Code(Counter(0)) at (prev + 5, 1) to (start + 1, 20)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
- Code(Counter(1)) at (prev + 2, 9) to (start + 0, 16)
- Code(Expression(0, Sub)) at (prev + 2, 9) to (start + 0, 15)
= (c0 - c1)
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 13:51:24 +10:00
- Code(Counter(0)) at (prev + 2, 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 13:13:05 +11:00
Highest counter ID seen: c1
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Function name: try_error_result::main
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
Raw bytes (26): 0x[01, 01, 01, 01, 05, 04, 01, 71, 01, 02, 0a, 05, 03, 05, 00, 06, 02, 02, 05, 00, 0b, 01, 01, 01, 00, 02]
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10: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-14 13:51:24 +10:00
Number of expressions: 1
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
- expression 0 operands: lhs = Counter(0), rhs = Counter(1)
Number of file 0 mappings: 4
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Counter(0)) at (prev + 113, 1) to (start + 2, 10)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
- Code(Counter(1)) at (prev + 3, 5) to (start + 0, 6)
- Code(Expression(0, Sub)) at (prev + 2, 5) to (start + 0, 11)
= (c0 - c1)
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 13:51:24 +10: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 13:13:05 +11:00
Highest counter ID seen: c1
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Function name: try_error_result::test1
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
Raw bytes (67): 0x[01, 01, 04, 07, 05, 01, 09, 05, 01, 05, 09, 0b, 01, 0d, 01, 02, 17, 05, 07, 09, 00, 0e, 09, 02, 09, 04, 1a, 02, 06, 0d, 00, 11, 02, 00, 29, 00, 2a, 00, 01, 0d, 00, 11, 00, 00, 2a, 00, 2b, 0a, 04, 0d, 00, 11, 00, 00, 2a, 00, 2b, 0e, 03, 05, 00, 0b, 01, 01, 01, 00, 02]
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Number of files: 1
- file 0 => global file 1
coverage: Eliminate more counters by giving them to unreachable nodes When preparing a function's coverage counters and metadata during codegen, any part of the original coverage graph that was removed by MIR optimizations can be treated as having an execution count of zero. Somewhat counter-intuitively, if we give those unreachable nodes a _higher_ priority for receiving physical counters (instead of counter expressions), that ends up reducing the total number of physical counters needed. This works because if a node is unreachable, we don't actually create a physical counter for it. Instead that node gets a fixed zero counter, and any other node that would have relied on that physical counter in its counter expression can just ignore that term completely.
2025-02-11 14:09:11 +11:00
Number of expressions: 4
- expression 0 operands: lhs = Expression(1, Add), rhs = Counter(1)
- expression 1 operands: lhs = Counter(0), rhs = Counter(2)
- expression 2 operands: lhs = Counter(1), rhs = Counter(0)
- expression 3 operands: lhs = Counter(1), rhs = Counter(2)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Number of file 0 mappings: 11
coverage: Add `#[rustfmt::skip]` to tests with non-standard formatting These tests deliberately use non-standard formatting, so that the line execution counts reported by `llvm-cov` reveal additional information about where code regions begin and end.
2024-01-16 13:40:01 +11:00
- Code(Counter(0)) at (prev + 13, 1) to (start + 2, 23)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
- Code(Counter(1)) at (prev + 7, 9) to (start + 0, 14)
- Code(Counter(2)) at (prev + 2, 9) to (start + 4, 26)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(0, Sub)) at (prev + 6, 13) to (start + 0, 17)
coverage: Eliminate more counters by giving them to unreachable nodes When preparing a function's coverage counters and metadata during codegen, any part of the original coverage graph that was removed by MIR optimizations can be treated as having an execution count of zero. Somewhat counter-intuitively, if we give those unreachable nodes a _higher_ priority for receiving physical counters (instead of counter expressions), that ends up reducing the total number of physical counters needed. This works because if a node is unreachable, we don't actually create a physical counter for it. Instead that node gets a fixed zero counter, and any other node that would have relied on that physical counter in its counter expression can just ignore that term completely.
2025-02-11 14:09:11 +11:00
= ((c0 + c2) - c1)
- Code(Expression(0, Sub)) at (prev + 0, 41) to (start + 0, 42)
= ((c0 + c2) - c1)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Zero) at (prev + 1, 13) to (start + 0, 17)
Enable by default.
2023-01-18 17:57:50 +00:00
- Code(Zero) at (prev + 0, 42) to (start + 0, 43)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(2, Sub)) at (prev + 4, 13) to (start + 0, 17)
coverage: Eliminate more counters by giving them to unreachable nodes When preparing a function's coverage counters and metadata during codegen, any part of the original coverage graph that was removed by MIR optimizations can be treated as having an execution count of zero. Somewhat counter-intuitively, if we give those unreachable nodes a _higher_ priority for receiving physical counters (instead of counter expressions), that ends up reducing the total number of physical counters needed. This works because if a node is unreachable, we don't actually create a physical counter for it. Instead that node gets a fixed zero counter, and any other node that would have relied on that physical counter in its counter expression can just ignore that term completely.
2025-02-11 14:09:11 +11:00
= (c1 - c0)
Enable by default.
2023-01-18 17:57:50 +00:00
- Code(Zero) at (prev + 0, 42) to (start + 0, 43)
coverage: Eliminate more counters by giving them to unreachable nodes When preparing a function's coverage counters and metadata during codegen, any part of the original coverage graph that was removed by MIR optimizations can be treated as having an execution count of zero. Somewhat counter-intuitively, if we give those unreachable nodes a _higher_ priority for receiving physical counters (instead of counter expressions), that ends up reducing the total number of physical counters needed. This works because if a node is unreachable, we don't actually create a physical counter for it. Instead that node gets a fixed zero counter, and any other node that would have relied on that physical counter in its counter expression can just ignore that term completely.
2025-02-11 14:09:11 +11:00
- Code(Expression(3, Sub)) at (prev + 3, 5) to (start + 0, 11)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c1 - c2)
coverage: Prefer to visit nodes whose predecessors have been visited
2024-12-05 18:57:17 +11:00
- Code(Counter(0)) at (prev + 1, 1) to (start + 0, 2)
coverage: Eliminate more counters by giving them to unreachable nodes When preparing a function's coverage counters and metadata during codegen, any part of the original coverage graph that was removed by MIR optimizations can be treated as having an execution count of zero. Somewhat counter-intuitively, if we give those unreachable nodes a _higher_ priority for receiving physical counters (instead of counter expressions), that ends up reducing the total number of physical counters needed. This works because if a node is unreachable, we don't actually create a physical counter for it. Instead that node gets a fixed zero counter, and any other node that would have relied on that physical counter in its counter expression can just ignore that term completely.
2025-02-11 14:09:11 +11:00
Highest counter ID seen: c2
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Function name: try_error_result::test2
coverage: Don't split bang-macro spans, just truncate them
2025-03-25 22:02:22 +11:00
Raw bytes (336): 0x[01, 01, 36, 0d, 11, 0d, 3f, 11, 15, 0d, 37, 3b, 1d, 3f, 19, 11, 15, 0d, 3f, 11, 15, 0d, 3b, 3f, 19, 11, 15, 0d, 37, 3b, 1d, 3f, 19, 11, 15, 41, 53, 21, 25, 41, 21, 41, 53, 21, 25, 09, 73, 77, 2d, 0d, 29, 09, 0d, 09, 77, 0d, 29, 09, 73, 77, 2d, 0d, 29, 45, 8b, 01, 31, 35, 45, 31, 45, 8b, 01, 31, 35, 49, 9f, 01, 39, 3d, 49, 39, 49, 9f, 01, 39, 3d, 05, 09, ab, 01, 09, af, 01, 3d, b3, 01, 39, b7, 01, 35, bb, 01, 31, bf, 01, 2d, c3, 01, 29, c7, 01, 25, cb, 01, 21, cf, 01, 1d, d3, 01, 19, d7, 01, 15, 05, 11, 28, 01, 3d, 01, 03, 17, 05, 08, 09, 00, 0e, 09, 02, 09, 04, 1a, 0d, 06, 0d, 00, 1f, 11, 00, 2f, 00, 30, 02, 00, 31, 03, 1c, 15, 04, 11, 00, 12, 1e, 02, 11, 03, 27, 32, 05, 11, 00, 14, 1e, 00, 17, 00, 29, 19, 00, 41, 00, 42, 26, 00, 43, 00, 47, 1d, 00, 5f, 00, 60, 32, 01, 0d, 00, 17, 4e, 01, 11, 00, 14, 41, 00, 17, 00, 29, 21, 00, 41, 00, 42, 4a, 00, 43, 00, 47, 25, 00, 60, 00, 61, 4e, 01, 0d, 00, 17, 6e, 04, 11, 00, 14, 62, 00, 17, 00, 29, 29, 00, 42, 00, 43, 66, 00, 44, 00, 48, 2d, 00, 61, 00, 62, 6e, 01, 0d, 00, 17, 86, 01, 01, 11, 00, 14, 45, 00, 17, 01, 1d, 31, 01, 36, 00, 37, 82, 01, 01, 12, 00, 16, 35, 00, 2f, 00, 30, 86, 01, 01, 0d, 00, 17, 9a, 01, 01, 11, 00, 14, 49, 00, 17, 01, 1d, 39, 02, 11, 00, 12, 96, 01, 01, 12, 00, 16, 3d, 01, 11, 00, 12, 9a, 01, 02, 0d, 00, 17, a2, 01, 03, 05, 00, 0b, a6, 01, 01, 01, 00, 02]
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Number of files: 1
- file 0 => global file 1
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
Number of expressions: 54
- expression 0 operands: lhs = Counter(3), rhs = Counter(4)
- expression 1 operands: lhs = Counter(3), rhs = Expression(15, Add)
- expression 2 operands: lhs = Counter(4), rhs = Counter(5)
- expression 3 operands: lhs = Counter(3), rhs = Expression(13, Add)
- expression 4 operands: lhs = Expression(14, Add), rhs = Counter(7)
- expression 5 operands: lhs = Expression(15, Add), rhs = Counter(6)
- expression 6 operands: lhs = Counter(4), rhs = Counter(5)
- expression 7 operands: lhs = Counter(3), rhs = Expression(15, Add)
- expression 8 operands: lhs = Counter(4), rhs = Counter(5)
- expression 9 operands: lhs = Counter(3), rhs = Expression(14, Add)
- expression 10 operands: lhs = Expression(15, Add), rhs = Counter(6)
- expression 11 operands: lhs = Counter(4), rhs = Counter(5)
- expression 12 operands: lhs = Counter(3), rhs = Expression(13, Add)
- expression 13 operands: lhs = Expression(14, Add), rhs = Counter(7)
- expression 14 operands: lhs = Expression(15, Add), rhs = Counter(6)
- expression 15 operands: lhs = Counter(4), rhs = Counter(5)
- expression 16 operands: lhs = Counter(16), rhs = Expression(20, Add)
- expression 17 operands: lhs = Counter(8), rhs = Counter(9)
- expression 18 operands: lhs = Counter(16), rhs = Counter(8)
- expression 19 operands: lhs = Counter(16), rhs = Expression(20, Add)
- expression 20 operands: lhs = Counter(8), rhs = Counter(9)
- expression 21 operands: lhs = Counter(2), rhs = Expression(28, Add)
- expression 22 operands: lhs = Expression(29, Add), rhs = Counter(11)
- expression 23 operands: lhs = Counter(3), rhs = Counter(10)
- expression 24 operands: lhs = Counter(2), rhs = Counter(3)
- expression 25 operands: lhs = Counter(2), rhs = Expression(29, Add)
- expression 26 operands: lhs = Counter(3), rhs = Counter(10)
- expression 27 operands: lhs = Counter(2), rhs = Expression(28, Add)
- expression 28 operands: lhs = Expression(29, Add), rhs = Counter(11)
- expression 29 operands: lhs = Counter(3), rhs = Counter(10)
- expression 30 operands: lhs = Counter(17), rhs = Expression(34, Add)
- expression 31 operands: lhs = Counter(12), rhs = Counter(13)
- expression 32 operands: lhs = Counter(17), rhs = Counter(12)
- expression 33 operands: lhs = Counter(17), rhs = Expression(34, Add)
- expression 34 operands: lhs = Counter(12), rhs = Counter(13)
- expression 35 operands: lhs = Counter(18), rhs = Expression(39, Add)
- expression 36 operands: lhs = Counter(14), rhs = Counter(15)
- expression 37 operands: lhs = Counter(18), rhs = Counter(14)
- expression 38 operands: lhs = Counter(18), rhs = Expression(39, Add)
- expression 39 operands: lhs = Counter(14), rhs = Counter(15)
- expression 40 operands: lhs = Counter(1), rhs = Counter(2)
- expression 41 operands: lhs = Expression(42, Add), rhs = Counter(2)
- expression 42 operands: lhs = Expression(43, Add), rhs = Counter(15)
- expression 43 operands: lhs = Expression(44, Add), rhs = Counter(14)
- expression 44 operands: lhs = Expression(45, Add), rhs = Counter(13)
- expression 45 operands: lhs = Expression(46, Add), rhs = Counter(12)
- expression 46 operands: lhs = Expression(47, Add), rhs = Counter(11)
- expression 47 operands: lhs = Expression(48, Add), rhs = Counter(10)
- expression 48 operands: lhs = Expression(49, Add), rhs = Counter(9)
- expression 49 operands: lhs = Expression(50, Add), rhs = Counter(8)
- expression 50 operands: lhs = Expression(51, Add), rhs = Counter(7)
- expression 51 operands: lhs = Expression(52, Add), rhs = Counter(6)
- expression 52 operands: lhs = Expression(53, Add), rhs = Counter(5)
- expression 53 operands: lhs = Counter(1), rhs = Counter(4)
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Number of file 0 mappings: 40
Tweak various coverage test files for slightly nicer formatting For coverage tests, splitting code across multiple lines often makes the resulting coverage report easier to interpret, so we force rustfmt to retain line breaks by adding dummy line comments with `//`.
2024-05-29 14:06:53 +10:00
- Code(Counter(0)) at (prev + 61, 1) to (start + 3, 23)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
- Code(Counter(1)) at (prev + 8, 9) to (start + 0, 14)
- Code(Counter(2)) at (prev + 2, 9) to (start + 4, 26)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Counter(3)) at (prev + 6, 13) to (start + 0, 31)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
- Code(Counter(4)) at (prev + 0, 47) to (start + 0, 48)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(0, Sub)) at (prev + 0, 49) to (start + 3, 28)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c3 - c4)
- Code(Counter(5)) at (prev + 4, 17) to (start + 0, 18)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(7, Sub)) at (prev + 2, 17) to (start + 3, 39)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c3 - (c4 + c5))
- Code(Expression(12, Sub)) at (prev + 5, 17) to (start + 0, 20)
= (c3 - (((c4 + c5) + c6) + c7))
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(7, Sub)) at (prev + 0, 23) to (start + 0, 41)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c3 - (c4 + c5))
- Code(Counter(6)) at (prev + 0, 65) to (start + 0, 66)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(9, Sub)) at (prev + 0, 67) to (start + 0, 71)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c3 - ((c4 + c5) + c6))
- Code(Counter(7)) at (prev + 0, 95) to (start + 0, 96)
coverage: Don't split bang-macro spans, just truncate them
2025-03-25 22:02:22 +11:00
- Code(Expression(12, Sub)) at (prev + 1, 13) to (start + 0, 23)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c3 - (((c4 + c5) + c6) + c7))
- Code(Expression(19, Sub)) at (prev + 1, 17) to (start + 0, 20)
= (c16 - (c8 + c9))
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Counter(16)) at (prev + 0, 23) to (start + 0, 41)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
- Code(Counter(8)) at (prev + 0, 65) to (start + 0, 66)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(18, Sub)) at (prev + 0, 67) to (start + 0, 71)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c16 - c8)
- Code(Counter(9)) at (prev + 0, 96) to (start + 0, 97)
coverage: Don't split bang-macro spans, just truncate them
2025-03-25 22:02:22 +11:00
- Code(Expression(19, Sub)) at (prev + 1, 13) to (start + 0, 23)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c16 - (c8 + c9))
- Code(Expression(27, Sub)) at (prev + 4, 17) to (start + 0, 20)
= (c2 - ((c3 + c10) + c11))
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(24, Sub)) at (prev + 0, 23) to (start + 0, 41)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c2 - c3)
- Code(Counter(10)) at (prev + 0, 66) to (start + 0, 67)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(25, Sub)) at (prev + 0, 68) to (start + 0, 72)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c2 - (c3 + c10))
- Code(Counter(11)) at (prev + 0, 97) to (start + 0, 98)
coverage: Don't split bang-macro spans, just truncate them
2025-03-25 22:02:22 +11:00
- Code(Expression(27, Sub)) at (prev + 1, 13) to (start + 0, 23)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c2 - ((c3 + c10) + c11))
- Code(Expression(33, Sub)) at (prev + 1, 17) to (start + 0, 20)
= (c17 - (c12 + c13))
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Counter(17)) at (prev + 0, 23) to (start + 1, 29)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
- Code(Counter(12)) at (prev + 1, 54) to (start + 0, 55)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(32, Sub)) at (prev + 1, 18) to (start + 0, 22)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c17 - c12)
- Code(Counter(13)) at (prev + 0, 47) to (start + 0, 48)
coverage: Don't split bang-macro spans, just truncate them
2025-03-25 22:02:22 +11:00
- Code(Expression(33, Sub)) at (prev + 1, 13) to (start + 0, 23)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c17 - (c12 + c13))
- Code(Expression(38, Sub)) at (prev + 1, 17) to (start + 0, 20)
= (c18 - (c14 + c15))
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Counter(18)) at (prev + 0, 23) to (start + 1, 29)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
- Code(Counter(14)) at (prev + 2, 17) to (start + 0, 18)
coverage: Shrink call spans to just the function name This is a way to shrink call spans that doesn't involve mixing different spans, and avoids overlap with argument spans. This patch also removes some low-value comments that were causing rustfmt to ignore the match arms.
2025-03-29 21:33:01 +11:00
- Code(Expression(37, Sub)) at (prev + 1, 18) to (start + 0, 22)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c18 - c14)
- Code(Counter(15)) at (prev + 1, 17) to (start + 0, 18)
coverage: Don't split bang-macro spans, just truncate them
2025-03-25 22:02:22 +11:00
- Code(Expression(38, Sub)) at (prev + 2, 13) to (start + 0, 23)
coverage: Completely overhaul counter assignment, using node-flow graphs
2025-01-12 21:36:07 +11:00
= (c18 - (c14 + c15))
- Code(Expression(40, Sub)) at (prev + 3, 5) to (start + 0, 11)
= (c1 - c2)
- Code(Expression(41, Sub)) at (prev + 1, 1) to (start + 0, 2)
= (((((((((((((c1 + c4) + c5) + c6) + c7) + c8) + c9) + c10) + c11) + c12) + c13) + c14) + c15) - c2)
Highest counter ID seen: c18
Copy most of `tests/run-coverage` into `tests/coverage-map/status-quo` The output of these tests is too complicated to comfortably verify by hand, but we can still use them to observe changes to the underlying mappings produced by codegen/LLVM. If these tests fail due to non-coverage changes (e.g. in HIR-to-MIR lowering or MIR optimizations), it should usually be OK to just `--bless` them, as long as the `run-coverage` test suite still works.
2023-08-14 21:29:41 +10:00
Reference in a new issue Copy permalink