diff options
| author | Manish Goregaokar <manishsmail@gmail.com> | 2020-07-02 00:16:30 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-07-02 00:16:30 -0700 |
| commit | dc762cea33a8b2f46c362d75f3d3327c88d1afe6 (patch) | |
| tree | 24ea9103d7885d79f0561325037c2e993d573fcf /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 500634bf1073248bb5b8561da3720a0820b09869 (diff) | |
| parent | 5239a68e72d1a0c7cba2cfd219a7da911360fbb7 (diff) | |
| download | rust-dc762cea33a8b2f46c362d75f3d3327c88d1afe6.tar.gz rust-dc762cea33a8b2f46c362d75f3d3327c88d1afe6.zip | |
Rollup merge of #73684 - richkadel:llvm-coverage-map-gen-2, r=wesleywiser
add spans to injected coverage counters, extract with CoverageData query This is the next iteration on the Rust Coverage implementation, and follows PR #73488 @tmandry @wesleywiser I came up with an approach for coverage spans, pushing them through the Call terminator as additional args so they can be extracted by the CoverageData query. I'm using an IndexVec to store them in CoverageData such that there can be only one per index (even if parts of the MIR get duplicated during optimization). If this approach works for you, I can quickly expand on this to build a separate IndexVec for counter expressions, using a separate call that will be ignored during code generation, but from which I can extract the counter expression values. Let me know your thoughts. Thanks! r? @tmandry Rust compiler MCP rust-lang/compiler-team#278 Relevant issue: #34701 - Implement support for LLVMs code coverage instrumentation
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions