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

// compile-flags: -C no-prepopulate-passes -Copt-level=0

// 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 float @llvm.sqrt.f32(float 4.000000e+00
        sqrt(4.0);
    }
}
Add more codegen tests 2022-12-30 14:11:30 -06:00			`// compile-flags: -C no-prepopulate-passes -Copt-level=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 04:32:52 -05:00
test: codegen: Add riscv abi llvm intrinsics test 2020-06-04 05:13:52 -05: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 04:32:52 -05: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 16:12:52 -05: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 04:32:52 -05: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
Add more codegen tests 2022-12-30 14:11:30 -06:00			`// CHECK: call float @llvm.sqrt.f32(float 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 04:32:52 -05:00			`sqrt(4.0);`
			`}`
			`}`