about summary refs log tree commit diff
path: root/compiler/rustc_lint/src
diff options
context:
space:
mode:
authorRich Kadel <richkadel@google.com>2020-08-27 14:13:04 -0700
committerRich Kadel <richkadel@google.com>2020-09-03 00:20:29 -0700
commit51d692cf7709de563cac6b5ee0080b8adf96f1df (patch)
treec557be235c6ef828d1517ca31d3a248d0d8e162b /compiler/rustc_lint/src
parente36e4bd0f7e722d3c97d1ca45387e58f81e4e8ea (diff)
downloadrust-51d692cf7709de563cac6b5ee0080b8adf96f1df.tar.gz
rust-51d692cf7709de563cac6b5ee0080b8adf96f1df.zip
Tools, tests, and experimenting with MIR-derived coverage counters
Adds a new mir_dump output file in HTML/CSS to visualize code regions
and the MIR features that they came from (including overlapping spans).
See example below:

Includes a basic, MIR-block-based implementation of coverage injection,
available via `-Zexperimental-coverage`. This implementation has known
flaws and omissions, but is simple enough to validate the new tools and
tests.

The existing `-Zinstrument-coverage` option currently enables
function-level coverage only, which at least appears to generate
accurate coverage reports at that level.

Experimental coverage is not accurate at this time. When branch coverage
works as intended, the `-Zexperimental-coverage` option should be
removed.

This PR replaces the bulk of PR #75828, with the remaining parts of
that PR distributed among other separate and indentpent PRs.

This PR depends on three of those other PRs: #76000, #76002, and

Rust compiler MCP rust-lang/compiler-team#278

Relevant issue: #34701 - Implement support for LLVMs code coverage
instrumentation

![Screen-Recording-2020-08-21-at-2](https://user-images.githubusercontent.com/3827298/90972923-ff417880-e4d1-11ea-92bb-8713c6198f6d.gif)
Diffstat (limited to 'compiler/rustc_lint/src')
0 files changed, 0 insertions, 0 deletions