Zalathar
339556eb02
coverage: Enlarge empty spans during MIR instrumentation, not codegen
...
This allows us to assume that coverage spans will only be discarded during
codegen in very unusual situations.
2025-05-10 00:24:01 +10:00
Zalathar
4d5a1acebf
coverage: Only merge adjacent coverage spans
...
This also removes some manipulation of the function signature span that only
made sense in the context of merging non-adjacent spans.
2025-05-06 20:42:25 +10:00
Zalathar
cc8336b6c1
coverage: Don't store a body span in FunctionCoverageInfo
2025-03-18 23:18:24 +11:00
Zalathar
20d051ec87
coverage: Defer part of counter-creation until codegen
2025-02-06 21:44:31 +11:00
Zalathar
ee7dc06cf1
coverage: Store BCB node IDs in mappings, and resolve them in codegen
...
Even though the coverage graph itself is no longer available during codegen,
its nodes can still be used as opaque IDs.
2025-02-06 21:44:29 +11:00
Zalathar
7f10ab2c98
coverage: Tweak FileCheck directives in a mir-opt test
2025-01-24 16:13:12 +11:00
Zalathar
34ed51cb83
coverage: Store coverage source regions as Span until codegen
2024-12-19 18:09:09 +11:00
Zalathar
9461f4296f
Revert "Rollup merge of #133418 - Zalathar:spans, r=jieyouxu"
...
This reverts commit adf9b5fcd1de43eaf0a779e10612caee8b47bede, reversing
changes made to af1ca153d4aed5ffe22445273aa388a8d3f8f4ae.
Reverting due to <https://github.com/rust-lang/rust/issues/133606 >.
2024-11-29 14:57:01 +11:00
Zalathar
b9fb1a69d2
coverage: Store coverage source regions as Span until codegen
2024-11-24 23:46:39 +11:00
Zalathar
996bdabc2a
coverage: Remove unhelpful code for handling multiple files per function
...
Functions currently can't have mappings in multiple files, and if that ever
changes (e.g. to properly support expansion regions), this code will need to be
completely overhauled anyway.
2024-11-08 20:43:08 +11:00
Zalathar
da37b14121
coverage: Move mir-opt coverage tests into a subdirectory
2024-04-22 21:55:33 +10:00
