diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-10-10 22:00:45 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-10-10 22:00:45 +0200 |
| commit | 13976f1f25ac64d53a2e1317153f4cfb1324b351 (patch) | |
| tree | dd0c0800e3defaf3a5bd073141e635690d6494c0 /tests/rustdoc-js-std/parser-errors.js | |
| parent | 8d94e06ec9758b5c03ea77bb5dab22a1a76bc261 (diff) | |
| parent | 207bc77e15acc9444bf6c3e74fa46607490a8e8a (diff) | |
| download | rust-13976f1f25ac64d53a2e1317153f4cfb1324b351.tar.gz rust-13976f1f25ac64d53a2e1317153f4cfb1324b351.zip | |
Rollup merge of #130308 - davidtwco:tied-target-consolidation, r=wesleywiser
codegen_ssa: consolidate tied target checks Fixes #105110. Fixes #105111. `rustc_codegen_llvm` and `rustc_codegen_gcc` duplicated logic for checking if tied target features were partially enabled. This PR consolidates these checks into `rustc_codegen_ssa` in the `codegen_fn_attrs` query, which also is run pre-monomorphisation for each function, which ensures that this check is run for unused functions, as would be expected. Also adds a test confirming that enabling one tied feature doesn't imply another - the appropriate error for this was already being emitted. I did a bisect and narrowed it down to two patches it was likely to be - something in #128796, probably #128221 or #128679.
Diffstat (limited to 'tests/rustdoc-js-std/parser-errors.js')
0 files changed, 0 insertions, 0 deletions