diff options
| author | Trevor Gross <tmgross@umich.edu> | 2025-07-05 01:46:49 -0500 |
|---|---|---|
| committer | Trevor Gross <tmgross@umich.edu> | 2025-07-05 02:02:09 -0500 |
| commit | c4d9c0f248f05542024ad55a52774ea84406db81 (patch) | |
| tree | 191074bbbaa7fe174bfd6c07fdf8bb7a9b1099e4 /compiler/rustc_pattern_analysis/src | |
| parent | 733b47ea4b1b86216f14ef56e49440c33933f230 (diff) | |
| download | rust-c4d9c0f248f05542024ad55a52774ea84406db81.tar.gz rust-c4d9c0f248f05542024ad55a52774ea84406db81.zip | |
tests: Use `cfg_target_has_reliable_f16_f128`
`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_pattern_analysis/src')
0 files changed, 0 insertions, 0 deletions