diff options
| author | bors <bors@rust-lang.org> | 2023-10-10 09:55:15 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-10-10 09:55:15 +0000 |
| commit | 5c37696f6026f91a869d51ab555cb0efae488972 (patch) | |
| tree | 68fb8a14033d0f0c91b9943c6916799284cc10c0 /compiler/rustc_codegen_gcc | |
| parent | 091bb74e7ed00e806f617d52f3159d4843460191 (diff) | |
| parent | 6c44425e98ff61bc59f1d58ce69768c310be5df8 (diff) | |
| download | rust-5c37696f6026f91a869d51ab555cb0efae488972.tar.gz rust-5c37696f6026f91a869d51ab555cb0efae488972.zip | |
Auto merge of #116409 - Zalathar:span-extraction, r=oli-obk
coverage: Separate initial span extraction from span processing One of the main subtasks of coverage instrumentation is looking through MIR to determine a list of source code spans that require coverage counters. That task is in turn subdivided into a few main steps: - Getting the initial spans from MIR statements/terminators - Processing the list of spans to merge or truncate nearby spans as necessary - Grouping the processed spans by their corresponding coverage graph node --- This PR enforces a firmer separation between the first two steps (span extraction and span processing), which ends up slightly simplifying both steps, since they don't need to deal with state that is only meaningful for the other step. --- `@rustbot` label +A-code-coverage
Diffstat (limited to 'compiler/rustc_codegen_gcc')
0 files changed, 0 insertions, 0 deletions