diff options
| author | Matthias Krüger <matthias.krueger@famsik.de> | 2024-11-10 10:09:52 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-11-10 10:09:52 +0100 |
| commit | 94cc01af159e2c086eeca2c9bf16fd3e60f04f43 (patch) | |
| tree | eaa801cd81b23e76a398cadd8fff5540905cdb8b /compiler/rustc_codegen_llvm/src/llvm_util.rs | |
| parent | 668959740f97e7a22ae340742886d330ab63950f (diff) | |
| parent | d199a63b1160f3eaab372aa969ab91248ee24315 (diff) | |
| download | rust-94cc01af159e2c086eeca2c9bf16fd3e60f04f43.tar.gz rust-94cc01af159e2c086eeca2c9bf16fd3e60f04f43.zip | |
Rollup merge of #132136 - RalfJung:target-feature-abi-compat, r=Mark-Simulacrum
ABI compatibility: remove section on target features Once https://github.com/rust-lang/rust/pull/127731 lands, we will properly diagnose ABI issues caused by target feature mismatch (at least on tier 1 targets). So I'd say we can remove the corresponding part of the docs here -- this is now something the compiler can take care of, so programmers don't need to be concerned. For now this is just a lint, but that's just a transition period, like in prior cases where we fix I-unsound bugs by adding a new check that goes through the "future incompatibility" stages. We have decided that it's actually a bug that we have ABI risks around target features, and we shouldn't document that bug as-if it was intended behavior. Cc `@rust-lang/opsem` `@chorman0773` `@veluca93`
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/llvm_util.rs')
0 files changed, 0 insertions, 0 deletions