diff options
| author | Stuart Cook <Zalathar@users.noreply.github.com> | 2024-12-31 14:12:47 +1100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-12-31 14:12:47 +1100 |
| commit | e49929e44d08aa94b4e1a5aab001c062b16c7680 (patch) | |
| tree | c174cf28187d969bfb7d31b75e1e6f5e7dd4cf34 /compiler/rustc_parse/src/parser/expr.rs | |
| parent | fa6990c16ec1f2535ad89d874e5ee4a0aaaae77a (diff) | |
| parent | c3189c585f9f8f80104d7b4791739f59eca405f7 (diff) | |
| download | rust-e49929e44d08aa94b4e1a5aab001c062b16c7680.tar.gz rust-e49929e44d08aa94b4e1a5aab001c062b16c7680.zip | |
Rollup merge of #134932 - RalfJung:arm-float-abi, r=workingjubilee
explicitly set float ABI for all ARM targets We currently always set the `FloatABIType` field in the LLVM target machine to `Default`, which means LLVM infers the ARM float ABI (hard vs soft) from the LLVM target triple. This causes problems such as having to set the LLVM triple to `*-gnueabi` for our `musleabi` targets to ensure they get correctly inferred as soft-float targets. It also means rustc doesn't really know which float ABI ends up being used, which is a blocker for https://github.com/rust-lang/rust/pull/134794. So I think we should stop doing that and instead explicitly control that value. That's what this PR implements. See [Zulip](https://rust-lang.zulipchat.com/#narrow/channel/187780-t-compiler.2Fwg-llvm/topic/Softfloat.20ABI.2C.20hardfloat.20instructions) for more context. Best reviewed commit-by-commit. I hope I got all those `llvm_floatabi` values right...
Diffstat (limited to 'compiler/rustc_parse/src/parser/expr.rs')
0 files changed, 0 insertions, 0 deletions