diff options
| author | Rich Kadel <richkadel@google.com> | 2020-12-11 18:28:37 -0800 |
|---|---|---|
| committer | Rich Kadel <richkadel@google.com> | 2020-12-11 21:40:22 -0800 |
| commit | eb963ffe451bfbc001ea86712a94619903bfbaf8 (patch) | |
| tree | 6cd2fb6ebdb047cbaef18e7358995ed9410a8db8 /compiler/rustc_interface/src | |
| parent | 9eb3a7ceafd1e2c1924177caa18c7cc0c25b413e (diff) | |
| download | rust-eb963ffe451bfbc001ea86712a94619903bfbaf8.tar.gz rust-eb963ffe451bfbc001ea86712a94619903bfbaf8.zip | |
Fixes reported bugs in Rust Coverage
Fixes: #79569 Fixes: #79566 Fixes: #79565 For the first issue (#79569), I got hit a `debug_assert!()` before encountering the reported error message (because I have `debug = true` enabled in my config.toml). The assertion showed me that some `SwitchInt`s can have more than one target pointing to the same `BasicBlock`. I had thought that was invalid, but since it seems to be possible, I'm allowing this now. I added a new test for this. ---- In the last two cases above, both tests (intentionally) fail to compile, but the `InstrumentCoverage` pass is invoked anyway. The MIR starts with an `Unreachable` `BasicBlock`, which I hadn't encountered before. (I had assumed the `InstrumentCoverage` pass would only be invoked with MIRs from successful compilations.) I don't have test infrastructure set up to test coverage on files that fail to compile, so I didn't add a new test.
Diffstat (limited to 'compiler/rustc_interface/src')
0 files changed, 0 insertions, 0 deletions