rust/tests/codegen/call-llvm-intrinsics.rs

// compile-flags: -C no-prepopulate-passes

// ignore-riscv64

#![feature(link_llvm_intrinsics)]
#![crate_type = "lib"]

struct A;

impl Drop for A {
    fn drop(&mut self) {
        println!("A");
    }
}

extern "C" {
    #[link_name = "llvm.sqrt.f32"]
    fn sqrt(x: f32) -> f32;
}

pub fn do_call() {
    let _a = A;

    unsafe {
        // Ensure that we `call` LLVM intrinsics instead of trying to `invoke` them
        // CHECK: call noundef float @llvm.sqrt.f32(float noundef 4.000000e+00
        sqrt(4.0);
    }
}
Use `call` instead of `invoke` for functions that cannot unwind The `FnAbi` now knows if the function is allowed to unwind. If a function isn't allowed to unwind, we can use a `call` instead of an `invoke`. This resolves an issue when calling LLVM intrinsics which cannot unwind LLVM will generate an error if you attempt to invoke them so we need to ignore cleanup blocks in codegen and generate a call instead. 2020-03-26 09:32:52 +00:00			`// compile-flags: -C no-prepopulate-passes`

test: codegen: Add riscv abi llvm intrinsics test 2020-06-04 10:13:52 +00:00			`// ignore-riscv64`

Use `call` instead of `invoke` for functions that cannot unwind The `FnAbi` now knows if the function is allowed to unwind. If a function isn't allowed to unwind, we can use a `call` instead of an `invoke`. This resolves an issue when calling LLVM intrinsics which cannot unwind LLVM will generate an error if you attempt to invoke them so we need to ignore cleanup blocks in codegen and generate a call instead. 2020-03-26 09:32:52 +00:00			`#![feature(link_llvm_intrinsics)]`
			`#![crate_type = "lib"]`

			`struct A;`

			`impl Drop for A {`
			`fn drop(&mut self) {`
			`println!("A");`
			`}`
			`}`

Update tests for extern block linting 2020-09-01 21:12:52 +00:00			`extern "C" {`
Use `call` instead of `invoke` for functions that cannot unwind The `FnAbi` now knows if the function is allowed to unwind. If a function isn't allowed to unwind, we can use a `call` instead of an `invoke`. This resolves an issue when calling LLVM intrinsics which cannot unwind LLVM will generate an error if you attempt to invoke them so we need to ignore cleanup blocks in codegen and generate a call instead. 2020-03-26 09:32:52 +00:00			`#[link_name = "llvm.sqrt.f32"]`
			`fn sqrt(x: f32) -> f32;`
			`}`

			`pub fn do_call() {`
			`let _a = A;`

			`unsafe {`
			// Ensure that we `call` LLVM intrinsics instead of trying to `invoke` them
Put `noundef` on all scalars that don't allow uninit Previously, it was only put on scalars with range validity invariants like bool, was uninit was obviously invalid for those. Since then, we have normatively declared all uninit primitives to be undefined behavior and can therefore put `noundef` on them. The remaining concern was the `mem::uninitialized` function, which cause quite a lot of UB in the older parts of the ecosystem. This function now doesn't return uninit values anymore, making users of it safe from this change. The only real sources of UB where people could encounter uninit primitives are `MaybeUninit::uninit().assume_init()`, which has always be clear in the docs about being UB and from heap allocations (like reading from the spare capacity of a vec. This is hopefully rare enough to not break anything. 2022-12-30 14:55:05 +00:00			`// CHECK: call noundef float @llvm.sqrt.f32(float noundef 4.000000e+00`
Use `call` instead of `invoke` for functions that cannot unwind The `FnAbi` now knows if the function is allowed to unwind. If a function isn't allowed to unwind, we can use a `call` instead of an `invoke`. This resolves an issue when calling LLVM intrinsics which cannot unwind LLVM will generate an error if you attempt to invoke them so we need to ignore cleanup blocks in codegen and generate a call instead. 2020-03-26 09:32:52 +00:00			`sqrt(4.0);`
			`}`
			`}`