rust/tests/codegen/issues/issue-84268.rs

//@ compile-flags: -O --crate-type=rlib
#![feature(intrinsics, repr_simd)]

extern "rust-intrinsic" {
    fn simd_fabs<T>(x: T) -> T;
    fn simd_eq<T, U>(x: T, y: T) -> U;
}

#[repr(simd)]
pub struct V([f32; 4]);

#[repr(simd)]
pub struct M([i32; 4]);

#[no_mangle]
// CHECK-LABEL: @is_infinite
pub fn is_infinite(v: V) -> M {
    // CHECK: fabs
    // CHECK: cmp oeq
    unsafe { simd_eq(simd_fabs(v), V([f32::INFINITY; 4])) }
}
Don't set `fast`(-math) for certain simd ops `fast-math` implies things like functions not being able to accept as an argument or return as a result, say, `inf` which made these functions confusingly named or behaving incorrectly, depending on how you interpret it. Since the time when these intrinsics have been implemented the intrinsics user's (stdsimd) approach has changed significantly and so now it is required that these intrinsics operate normally rather than in "whatever" way. Fixes #84268 2021-04-17 12:40:59 -05:00			`//@ compile-flags: -O --crate-type=rlib`
fix use of platform_intrinsics in tests 2024-02-23 11:36:24 -06:00			`#![feature(intrinsics, repr_simd)]`
Don't set `fast`(-math) for certain simd ops `fast-math` implies things like functions not being able to accept as an argument or return as a result, say, `inf` which made these functions confusingly named or behaving incorrectly, depending on how you interpret it. Since the time when these intrinsics have been implemented the intrinsics user's (stdsimd) approach has changed significantly and so now it is required that these intrinsics operate normally rather than in "whatever" way. Fixes #84268 2021-04-17 12:40:59 -05:00
fix use of platform_intrinsics in tests 2024-02-23 11:36:24 -06:00			`extern "rust-intrinsic" {`
Don't set `fast`(-math) for certain simd ops `fast-math` implies things like functions not being able to accept as an argument or return as a result, say, `inf` which made these functions confusingly named or behaving incorrectly, depending on how you interpret it. Since the time when these intrinsics have been implemented the intrinsics user's (stdsimd) approach has changed significantly and so now it is required that these intrinsics operate normally rather than in "whatever" way. Fixes #84268 2021-04-17 12:40:59 -05:00			`fn simd_fabs<T>(x: T) -> T;`
			`fn simd_eq<T, U>(x: T, y: T) -> U;`
			`}`

			`#[repr(simd)]`
			`pub struct V([f32; 4]);`

			`#[repr(simd)]`
			`pub struct M([i32; 4]);`

			`#[no_mangle]`
			`// CHECK-LABEL: @is_infinite`
			`pub fn is_infinite(v: V) -> M {`
			`// CHECK: fabs`
			`// CHECK: cmp oeq`
Run rustfmt on `tests/codegen/`. Except for `simd-intrinsic/`, which has a lot of files containing multiple types like `u8x64` which really are better when hand-formatted. There is a surprising amount of two-space indenting in this directory. Non-trivial changes: - `rustfmt::skip` needed in `debug-column.rs` to preserve meaning of the test. - `rustfmt::skip` used in a few places where hand-formatting read more nicely: `enum/enum-match.rs` - Line number adjustments needed for the expected output of `debug-column.rs` and `coroutine-debug.rs`. 2024-05-28 23:11:20 -05:00			`unsafe { simd_eq(simd_fabs(v), V([f32::INFINITY; 4])) }`
Don't set `fast`(-math) for certain simd ops `fast-math` implies things like functions not being able to accept as an argument or return as a result, say, `inf` which made these functions confusingly named or behaving incorrectly, depending on how you interpret it. Since the time when these intrinsics have been implemented the intrinsics user's (stdsimd) approach has changed significantly and so now it is required that these intrinsics operate normally rather than in "whatever" way. Fixes #84268 2021-04-17 12:40:59 -05:00			`}`