diff options
| author | bors <bors@rust-lang.org> | 2020-07-29 20:35:52 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-07-29 20:35:52 +0000 |
| commit | db0492ace429cfeb3567e2c04e300be7df9972ff (patch) | |
| tree | bdaef57c8b3bace8e9939edd479d945a2da53633 /src/test/rustdoc-ui/coverage/doc-examples.rs | |
| parent | 8611e526b766ce188dc29bd49bf66ff17764ceea (diff) | |
| parent | 5b2e2b25e41afbbd0ad803f7986d8559ef649a7e (diff) | |
| download | rust-db0492ace429cfeb3567e2c04e300be7df9972ff.tar.gz rust-db0492ace429cfeb3567e2c04e300be7df9972ff.zip | |
Auto merge of #74733 - richkadel:llvm-coverage-map-gen-5, r=tmandry
Fixed coverage map issues; better aligned with LLVM APIs Found some problems with the coverage map encoding when testing with more than one counter per function. While debugging, I realized some better ways to structure the Rust implementation of the coverage mapping generator. I refactored somewhat, resulting in less code overall, expanded coverage of LLVM Coverage Map capabilities, and much closer alignment with LLVM data structures, APIs, and naming. This should be easier to follow and easier to maintain. r? @tmandry Rust compiler MCP rust-lang/compiler-team#278 Relevant issue: #34701 - Implement support for LLVMs code coverage instrumentation
Diffstat (limited to 'src/test/rustdoc-ui/coverage/doc-examples.rs')
0 files changed, 0 insertions, 0 deletions