3 Commits

Author	SHA1	Message	Date
Zalathar	86a66c8171	coverage: Store each BCB's code regions in one coverage statement ... If a BCB has more than one code region, those extra regions can now all be stored in the same coverage statement, instead of being stored in additional statements.	2023-10-03 13:03:39 +11:00
Zalathar	59a11af1f9	coverage: Mappings for unused functions can all be zero ... There is no need to include a dummy counter reference in the coverage mappings for an unused function.	2023-10-03 13:03:39 +11:00
Zalathar	3141177995	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-09-05 11:55:34 +10:00