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 | 2ca575348df1ba7b0116dfc5f73a173ef4e168a3 (patch) | |
| tree | 3dfc406fd6c71ff6abe27361585fe2c5fb4031ec /tests/codegen/patchable-function-entry | |
| parent | e0bb4178c0e02b493f822b908c0231f150bfc4c5 (diff) | |
| parent | 73c192b931c9c3587941574bbd03aae1b77e3d94 (diff) | |
| download | rust-2ca575348df1ba7b0116dfc5f73a173ef4e168a3.tar.gz rust-2ca575348df1ba7b0116dfc5f73a173ef4e168a3.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/codegen/patchable-function-entry')
0 files changed, 0 insertions, 0 deletions