rust/tests/coverage/tight_inf_loop.cov-map

Function name: tight_inf_loop::main
Raw bytes (21): 0x[01, 01, 01, 01, 00, 03, 01, 01, 01, 01, 0d, 00, 02, 09, 00, 10, 02, 01, 06, 01, 02]
Number of files: 1
- file 0 => global file 1
Number of expressions: 1
- expression 0 operands: lhs = Counter(0), rhs = Zero
Number of file 0 mappings: 3
- Code(Counter(0)) at (prev + 1, 1) to (start + 1, 13)
- Code(Zero) at (prev + 2, 9) to (start + 0, 16)
- Code(Expression(0, Sub)) at (prev + 1, 6) to (start + 1, 2)
    = (c0 - Zero)
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 06:29:41 -05:00			`Function name: tight_inf_loop::main`
coverage: Consistently remove unused counter IDs from expressions/mappings 2023-10-24 06:48:59 -05:00			`Raw bytes (21): 0x[01, 01, 01, 01, 00, 03, 01, 01, 01, 01, 0d, 00, 02, 09, 00, 10, 02, 01, 06, 01, 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 06:29:41 -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`
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 06:29:41 -05:00			`Number of file 0 mappings: 3`
			`- Code(Counter(0)) at (prev + 1, 1) to (start + 1, 13)`
			`- Code(Zero) at (prev + 2, 9) to (start + 0, 16)`
			`- Code(Expression(0, Sub)) at (prev + 1, 6) to (start + 1, 2)`
coverage: Consistently remove unused counter IDs from expressions/mappings 2023-10-24 06:48:59 -05:00			`= (c0 - Zero)`
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 06:29:41 -05:00