nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-26 08:44:35 +00:00
Code Issues Packages Projects Releases Wiki Activity
a993a8bf3f
rust/tests/coverage-map
History
Zalathar 527c629cd9 coverage: Explicitly simplify coverage expressions in codegen 
After coverage instrumentation and MIR transformations, we can sometimes end up
with coverage expressions that always have a value of zero. Any expression
operand that refers to an always-zero expression can be replaced with a literal
`Operand::Zero`, making the emitted coverage mapping data smaller and simpler.

This simplification step is mostly redundant with the simplifications performed
inline in `expressions_with_regions`, except that it does a slightly more
thorough job in some cases (because it checks for always-zero expressions
*after* other simplifications).

However, adding this simplification step will then let us greatly simplify that
code, without affecting the quality of the emitted coverage maps.
2023-09-21 18:32:49 +10:00
..
status-quo coverage: Explicitly simplify coverage expressions in codegen 2023-09-21 18:32:49 +10:00
if.cov-map Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
if.rs Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
long_and_wide.cov-map Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
long_and_wide.rs Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
README.md Copy most of tests/run-coverage into tests/coverage-map/status-quo 2023-09-05 11:55:34 +10:00
trivial.cov-map Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00
trivial.rs Add test suite coverage-map to test coverage mappings emitted by LLVM 2023-09-05 11:55:17 +10:00

README.md

The tests in ./status-quo were copied from tests/run-coverage in order to capture the current behavior of the instrumentor on non-trivial programs. The actual mappings have not been closely inspected.

Maintenance note

These tests can be sensitive to small changes in MIR spans or MIR control flow, especially in HIR-to-MIR lowering or MIR optimizations.

If you haven't touched the coverage code directly, and the run-coverage test suite still works, then it should usually be OK to just --bless these coverage mapping tests as necessary, without worrying too much about the exact changes.