rust/compiler/rustc_target at e8a28e78a947c2233abbc47ec00bcd8513df7239 - rust

mirror of https://github.com/rust-lang/rust.git synced 2026-04-27 18:57:42 +03:00

Files

T

Jonathan Brouwer ca1b24406d Rollup merge of #152941 - RalfJung:abi-control, r=mati865

prefer actual ABI-controling fields over target.abi when making ABI decisions

We don't actually check that `abi` is consistent with the fields that control the ABI, e.g. one could set `llvm_abiname` to "ilp32e" on a riscv target without setting a matching `abi`. So, if we need to make actual decisions, better to use the source of truth we forward to LLVM than the informational string we forward to the user.

This is a breaking change for aarch64 JSON target specs: setting `abi` to "softfloat" is no longer enough; one has to also set `rustc_abi` to "softfloat". That is consistent with riscv and arm32, but it's still surprising. Cc @Darksonn in case this affects the Linux kernel.

Also see https://github.com/rust-lang/rust/pull/153035 which does something similar for PowerPC, and [Zulip](https://rust-lang.zulipchat.com/#narrow/channel/131828-t-compiler/topic/De-spaghettifying.20ABI.20controls/with/575095372). Happy to delay this PR if someone has a better idea.

Cc @folkertdev @workingjubilee

2026-03-03 07:14:11 +01:00

src

Rollup merge of #152941 - RalfJung:abi-control, r=mati865

2026-03-03 07:14:11 +01:00

Cargo.toml

Add --print target-spec-json-schema

2025-09-12 20:53:28 +02:00

README.md

Fix outdated crate names in compiler docs

2021-04-08 11:12:14 -05:00

README.md

rustc_target contains some very low-level details that are specific to different compilation targets and so forth.

For more information about how rustc works, see the rustc dev guide.