rust/library/compiler-builtins/libm/build.rs

use std::env;

mod configure;

fn main() {
    let cfg = configure::Config::from_env();

    println!("cargo:rerun-if-changed=build.rs");
    println!("cargo:rerun-if-changed=configure.rs");
    println!("cargo:rustc-check-cfg=cfg(assert_no_panic)");

    // If set, enable `no-panic`. Requires LTO (`release-opt` profile).
    if env::var("ENSURE_NO_PANIC").is_ok() {
        println!("cargo:rustc-cfg=assert_no_panic");
    }

    configure::emit_libm_config(&cfg);
}
Overhaul tests * Move everything to azure pipelines * Inline docker configuration in this repo (no `cross`) * Delete `no-panic` example, use `#[no_panic]` instead. 2019-05-02 11:37:21 -07:00			`use std::env;`

Add `f16` and `f128` configuration from `compiler-builtins` In preparation of adding routines from these two types, duplicate the `compiler-builtins` configuration here. 2024-10-26 00:44:50 -05:00			`mod configure;`

Rework how testing is done Use a build script to generate musl reference outputs and then ensure that everything gets hooked up to actually run reference tests. 2019-05-02 10:48:55 -07:00			`fn main() {`
Add `f16` and `f128` configuration from `compiler-builtins` In preparation of adding routines from these two types, duplicate the `compiler-builtins` configuration here. 2024-10-26 00:44:50 -05:00			`let cfg = configure::Config::from_env();`

Rework how testing is done Use a build script to generate musl reference outputs and then ensure that everything gets hooked up to actually run reference tests. 2019-05-02 10:48:55 -07:00			`println!("cargo:rerun-if-changed=build.rs");`
refactor: Move the `libm` crate to a subdirectory In preparation for switching to a virtual manifest, move the `libm` crate into a subdirectory and update paths to match. Updating `Cargo.toml` is done in the next commit so git tracks the moved file correctly. 2025-04-09 01:21:33 +00:00			`println!("cargo:rerun-if-changed=configure.rs");`
Change `build.rs` to use the older `:` rather than `::` This allows supporting Rust < 1.77. 2024-10-27 22:45:37 -05:00			`println!("cargo:rustc-check-cfg=cfg(assert_no_panic)");`
Rework how testing is done Use a build script to generate musl reference outputs and then ensure that everything gets hooked up to actually run reference tests. 2019-05-02 10:48:55 -07:00
Rework the available Cargo profiles Currently the default release profile enables LTO and single CGU builds, which is very slow to build. Most tests are better run with optimizations enabled since it allows testing a much larger number of inputs, so it is inconvenient that building can sometimes take significantly longer than the tests. Remedy this by doing the following: * Move the existing `release` profile to `release-opt`. * With the above, the default `release` profile is untouched (16 CGUs and thin local LTO). * `release-checked` inherits `release`, so no LTO or single CGU. This means that the simple `cargo test --release` becomes much faster for local development. We are able to enable the other profiles as needed in CI. Tests should ideally still be run with `--profile release-checked` to ensure there are no debug assetions or unexpected wrapping math hit. `no-panic` still needs a single CGU, so must be run with `--profile release-opt`. Since it is not possible to detect CGU or profilel configuration from within build scripts, the `ENSURE_NO_PANIC` environment variable must now always be set. 2025-01-25 05:22:11 +00:00			// If set, enable `no-panic`. Requires LTO (`release-opt` profile).
			`if env::var("ENSURE_NO_PANIC").is_ok() {`
Remove remnants of the `checked` feature The Cargo feature `checked` was added in 410b0633a6b9 ("Overhaul tests") and later removed in e4ac1399062c ("swap stable to be unstable, checked is now debug_assertions"). However, there are a few remaining uses of `feature = "checked"` that did not get removed. Clean these up here. 2025-01-25 04:18:44 +00:00			`println!("cargo:rustc-cfg=assert_no_panic");`
Overhaul tests * Move everything to azure pipelines * Inline docker configuration in this repo (no `cross`) * Delete `no-panic` example, use `#[no_panic]` instead. 2019-05-02 11:37:21 -07:00			`}`
Replace `feature = "unstable-intrinsics"` with `intrinsics_enabled` We currently have a non-additive feature, "force-soft-floats", and we will need to gain another "no-f16-f128". This makes `cfg` usage in code somewhat confusing and redundant. Use `build.rs` to figure out if "unstable-intrinsics" is enabled while "force-soft-floats" is not enabled and if so, emit a cfg `intrinsics_enabled`. This is cleaner to use and should make adding more features easier to reason about. Also use this as an opportunity to eliminate the build.rs from the compiler-builtins test crate, replaced with the `[lints]` table in Cargo.toml. 2024-10-28 18:15:19 -05:00
Add `f16` and `f128` configuration from `compiler-builtins` In preparation of adding routines from these two types, duplicate the `compiler-builtins` configuration here. 2024-10-26 00:44:50 -05:00			`configure::emit_libm_config(&cfg);`
Add an "arch" Cargo feature that is on by default Introduce a Cargo feature to enable or disable architecture-specific features (SIMD, assembly), which is on by default. This allows for more fine grained control compared to relying on the `force-soft-floats` feature. Similar to "unstable-intrinsics", introduce a build.rs config option for `unstable-intrinsics AND NOT force-soft-floats`, which makes this easier to work with in code. Effectively, this allows moving our non-additive Cargo feature (force-soft-floats) to a positive one by default, allowing for an override when needed. 2024-10-28 20:24:46 -05:00			`}`