diff options
| author | Michael Goulet <michael@errs.io> | 2024-01-05 10:57:21 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-05 10:57:21 -0500 |
| commit | e74a0cdfeda0738097e5f261048b4293c36f41e3 (patch) | |
| tree | 163307f8e0f60235884d54c2ed4fdfbc6343cfc3 /compiler/rustc_codegen_llvm/src/llvm_util.rs | |
| parent | f361b591efb7c05b9f498f2b4eb6381d522094ce (diff) | |
| parent | af3205421ff989c143e09b6e96413eadaa1dbc4d (diff) | |
| download | rust-e74a0cdfeda0738097e5f261048b4293c36f41e3.tar.gz rust-e74a0cdfeda0738097e5f261048b4293c36f41e3.zip | |
Rollup merge of #119566 - Zalathar:remove-spanview, r=Swatinem,Nilstrieb
Remove `-Zdump-mir-spanview` The `-Zdump-mir-spanview` flag was added back in #76074, as a development/debugging aid for the initial work on what would eventually become `-Cinstrument-coverage`. It causes the compiler to emit an HTML file containing a function's source code, with various spans highlighted based on the contents of MIR. When the suggestion was made to [triage and remove unnecessary `-Z` flags (Zulip)](https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/.60-Z.60.20option.20triage), I noted that this flag could potentially be worth removing, but I wanted to keep it around to see whether I found it useful for my own coverage work. But when I actually tried to use it, I ran into various issues (e.g. it crashes on `tests/coverage/closure.rs`). If I can't trust it to work properly without a full overhaul, then instead of diving down a rabbit hole of trying to fix arcane span-handling bugs, it seems better to just remove this obscure old code entirely. --- ````@rustbot```` label +A-code-coverage
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/llvm_util.rs')
0 files changed, 0 insertions, 0 deletions
