mirror of
https://github.com/rust-lang/rust.git
synced 2025-06-22 12:37:32 +00:00
55b3f8b13d
Since updating the docker images in <https://github.com/rust-lang/compiler-builtins/pull/625>, it looks like `__extendhftf2` and `__trunctfhf2` are available on all 64-bit Linux platforms.
70 lines
2.8 KiB
Rust
70 lines
2.8 KiB
Rust
use std::{collections::HashSet, env};
|
|
|
|
/// Features to enable
|
|
#[derive(Debug, PartialEq, Eq, Hash)]
|
|
enum Feature {
|
|
NoSysF128,
|
|
NoSysF128IntConvert,
|
|
NoSysF16,
|
|
NoSysF16F128Convert,
|
|
}
|
|
|
|
fn main() {
|
|
let target = env::var("TARGET").unwrap();
|
|
let mut features = HashSet::new();
|
|
|
|
// These platforms do not have f128 symbols available in their system libraries, so
|
|
// skip related tests.
|
|
if target.starts_with("arm-")
|
|
|| target.contains("apple-darwin")
|
|
|| target.contains("windows-msvc")
|
|
// GCC and LLVM disagree on the ABI of `f16` and `f128` with MinGW. See
|
|
// <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115054>.
|
|
|| target.contains("windows-gnu")
|
|
// FIXME(llvm): There is an ABI incompatibility between GCC and Clang on 32-bit x86.
|
|
// See <https://github.com/llvm/llvm-project/issues/77401>.
|
|
|| target.starts_with("i686")
|
|
// 32-bit PowerPC and 64-bit LE gets code generated that Qemu cannot handle. See
|
|
// <https://github.com/rust-lang/compiler-builtins/pull/606#issuecomment-2105635926>.
|
|
|| target.starts_with("powerpc-")
|
|
|| target.starts_with("powerpc64le-")
|
|
// FIXME: We get different results from the builtin functions. See
|
|
// <https://github.com/rust-lang/compiler-builtins/pull/606#issuecomment-2105657287>.
|
|
|| target.starts_with("powerpc64-")
|
|
{
|
|
features.insert(Feature::NoSysF128);
|
|
features.insert(Feature::NoSysF128IntConvert);
|
|
features.insert(Feature::NoSysF16F128Convert);
|
|
}
|
|
|
|
if target.starts_with("i586") || target.starts_with("i686") {
|
|
// 32-bit x86 does not have `__fixunstfti`/`__fixtfti` but does have everything else
|
|
features.insert(Feature::NoSysF128IntConvert);
|
|
// FIXME: 32-bit x86 has a bug in `f128 -> f16` system libraries
|
|
features.insert(Feature::NoSysF16F128Convert);
|
|
}
|
|
|
|
if target.starts_with("wasm32-") {
|
|
// Linking says "error: function signature mismatch: __extendhfsf2" and seems to
|
|
// think the signature is either `(i32) -> f32` or `(f32) -> f32`
|
|
features.insert(Feature::NoSysF16);
|
|
}
|
|
|
|
for feature in features {
|
|
let (name, warning) = match feature {
|
|
Feature::NoSysF128 => ("no-sys-f128", "using apfloat fallback for f128"),
|
|
Feature::NoSysF128IntConvert => (
|
|
"no-sys-f128-int-convert",
|
|
"using apfloat fallback for f128 to int conversions",
|
|
),
|
|
Feature::NoSysF16F128Convert => (
|
|
"no-sys-f16-f128-convert",
|
|
"skipping using apfloat fallback for f16 <-> f128 conversions",
|
|
),
|
|
Feature::NoSysF16 => ("no-sys-f16", "using apfloat fallback for f16"),
|
|
};
|
|
println!("cargo:warning={warning}");
|
|
println!("cargo:rustc-cfg=feature=\"{name}\"");
|
|
}
|
|
}
|