diff options
| author | Trevor Gross <t.gross35@gmail.com> | 2025-07-08 22:50:28 -0500 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-08 22:50:28 -0500 |
| commit | 4a4985a924e7745926aee1673ddc1b615414f209 (patch) | |
| tree | 4fddd0d64591495b36ea8fc0383125c8abbd2144 /compiler/rustc_codegen_llvm/src/lib.rs | |
| parent | 0d99b5585b5f0d69f162472a83134e277a6c3839 (diff) | |
| parent | c4d9c0f248f05542024ad55a52774ea84406db81 (diff) | |
| download | rust-4a4985a924e7745926aee1673ddc1b615414f209.tar.gz rust-4a4985a924e7745926aee1673ddc1b615414f209.zip | |
Rollup merge of #143475 - tgross35:runtime-test-config, r=jieyouxu
tests: Use `cfg_target_has_reliable_f16_f128` in `conv-bits-runtime-const`
`conv-bits-runtime-const` gates `f16` and `f128` tests behind `x86_64`, but this isn't always accurate. In particular, x86 `MinGW` has an ABI bug [1] which means things work when linked to our Rust math libraries but don't work with host libraries. RUST-143405 slightly adjusts which targets we provide `f16` and `f128` symbols for and effectively removes MinGW from that list, meaning host libraries start getting linked, meaning `f16` and `f128` tests start to fail.
Account for this by changing the gates in one such test to `cfg(target_has_reliable_{f16,f128})` which is the way we should be gating all behavior related to the types going forward.
`rustfmt` also seems to have formatted the macros which is fine.
[1]: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115054
Diffstat (limited to 'compiler/rustc_codegen_llvm/src/lib.rs')
0 files changed, 0 insertions, 0 deletions