about summary refs log tree commit diff
path: root/compiler/rustc_mir_transform/src/coverage/graph.rs
diff options
context:
space:
mode:
authorJacob Pratt <jacob@jhpratt.dev>2025-01-08 00:52:49 -0500
committerGitHub <noreply@github.com>2025-01-08 00:52:49 -0500
commit57eb95ca6fe7cdacdf1c272ae106846ae3117f91 (patch)
tree3c60673371f6b8d871429f7b10927e3cdb7dff50 /compiler/rustc_mir_transform/src/coverage/graph.rs
parent45250f367ffa6c4325c05f10a87071742279c07f (diff)
parent427abb69bf4c788504fa454fa03559e815c682df (diff)
downloadrust-57eb95ca6fe7cdacdf1c272ae106846ae3117f91.tar.gz
rust-57eb95ca6fe7cdacdf1c272ae106846ae3117f91.zip
Rollup merge of #135203 - RalfJung:arm-soft-float, r=workingjubilee
arm: add unstable soft-float target feature

This has an actual usecase as mentioned [here](https://github.com/rust-lang/rust/issues/116344#issuecomment-2575324988), and with my recent ARM float ABI changes there shouldn't be any soundness concerns any more. We will reject enabling this feature on `hf` targets, but disabling it on non-`hf` targets is entirely fine -- the target feature refers to whether softfloat emulation is used for float instructions, and is independent of the ABI which we set separately via `llvm_floatabi`.

Cc ``@workingjubilee``
Diffstat (limited to 'compiler/rustc_mir_transform/src/coverage/graph.rs')
0 files changed, 0 insertions, 0 deletions