diff options
| author | bors <bors@rust-lang.org> | 2023-09-05 15:30:59 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2023-09-05 15:30:59 +0000 |
| commit | ab45885dec2a6552cb060a5b7183653baaecd580 (patch) | |
| tree | cbc89120fae2ede8bdc74e158fb7724cbe567852 /src/llvm-project | |
| parent | f222a2dd8f6391e6433f57a7c5f1514166edbec1 (diff) | |
| parent | 3141177995f52fc3cbb64d66cf0a98ea0f754fca (diff) | |
| download | rust-ab45885dec2a6552cb060a5b7183653baaecd580.tar.gz rust-ab45885dec2a6552cb060a5b7183653baaecd580.zip | |
Auto merge of #114843 - Zalathar:test-coverage-map, r=oli-obk
coverage: Explicitly test the coverage maps produced by codegen/LLVM Our existing coverage tests verify the output of end-to-end coverage reports, but we don't have any way to test the specific mapping information (code regions and their associated counters) that are emitted by `rustc_codegen_llvm` and LLVM. That makes it harder to to be confident in changes that would modify those mappings (whether deliberately or accidentally). This PR addresses that by adding a new `coverage-map` test suite that does the following: - Compiles test files to LLVM IR assembly (`.ll`) - Feeds those IR files to a custom tool (`src/tools/coverage-dump`) that extracts and decodes coverage mappings, and prints them in a more human-readable format - Checks the output of that tool against known-good snapshots --- I recommend excluding the last commit while reviewing the main changes, because that last commit is just ~40 test files copied over from `tests/run-coverage`, plus their blessed coverage-map snapshots and a readme file. Those snapshots aren't really intended to be checked by hand; they're mostly there to increase the chances that an unintended change to coverage maps will be observable (even if it requires relatively specific circumstances to manifest).
Diffstat (limited to 'src/llvm-project')
0 files changed, 0 insertions, 0 deletions
