diff options
| author | Yuki Okushi <huyuumi.dev@gmail.com> | 2020-11-03 15:27:16 +0900 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-11-03 15:27:16 +0900 |
| commit | 8894c903cb02f8abde4d2d2b288320bc0930b8f9 (patch) | |
| tree | b19509fe573b4ac806ba2ba145465752e5092999 /compiler/rustc_codegen_llvm/src/lib.rs | |
| parent | 416dd6757b42089d63e3f2899adfcfe1e25bd0fd (diff) | |
| parent | 6c1f15fa81be5f89cd7af7f7e73012967b4e673a (diff) | |
| download | rust-8894c903cb02f8abde4d2d2b288320bc0930b8f9.tar.gz rust-8894c903cb02f8abde4d2d2b288320bc0930b8f9.zip | |
Rollup merge of #78663 - Aaron1011:fix/cap-future-compat, r=tmandry
Fix ICE when a future-incompat-report has its command-line level capped Fixes #78660 With PR https://github.com/rust-lang/rust/pull/75534 merged, we now run more lint-related code for future-incompat-report, even when their final level is Allow. Some lint-related code was not expecting `Level::Allow`, and had an explicit panic. This PR explicitly tracks the lint level set on the command line before `--cap-lints` is applied. This is used to emit a more precise error note (e.g. we don't say that `-W lint-name` was specified on the command line just because a lint was capped to Warn). As a result, we can now correctly emit a note that `-A` was used if we got `Level::Allow` from the command line (before the cap is applied).
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/lib.rs')
0 files changed, 0 insertions, 0 deletions