rust/tests/ui/asm/naked-functions-ffi.rs

//@ check-pass
//@ needs-asm-support
#![feature(naked_functions)]
#![crate_type = "lib"]

use std::arch::naked_asm;

#[naked]
pub extern "C" fn naked(p: char) -> u128 {
    //~^ WARN uses type `char`
    //~| WARN uses type `u128`
    unsafe {
        naked_asm!("");
    }
}
Validate FFI-safety warnings on naked functions Test that FFI-safety warnings don't get accidentally dropped on naked functions. The big picture is that if you implement a naked function with the Rust ABI you'll get a warning. Further, if you implement a naked function with a standardized ABI, but use non-FFI-safe types you will still get a warning. rust-lang/rfcs#2774 rust-lang/rfcs#2972 2021-08-03 16:43:21 -05:00			`//@ check-pass`
Disable some tests for platforms without registers. Update new tests to run on aarch64 platforms. 2021-09-06 10:44:19 -05:00			`//@ needs-asm-support`
Validate FFI-safety warnings on naked functions Test that FFI-safety warnings don't get accidentally dropped on naked functions. The big picture is that if you implement a naked function with the Rust ABI you'll get a warning. Further, if you implement a naked function with a standardized ABI, but use non-FFI-safe types you will still get a warning. rust-lang/rfcs#2774 rust-lang/rfcs#2972 2021-08-03 16:43:21 -05:00			`#![feature(naked_functions)]`
			`#![crate_type = "lib"]`

use `naked_asm!` in naked-function tests 2024-08-04 09:45:48 -05:00			`use std::arch::naked_asm;`
Stabilize asm! and global_asm! They are also removed from the prelude as per the decision in https://github.com/rust-lang/rust/issues/87228. stdarch and compiler-builtins are updated to work with the new, stable asm! and global_asm! macros. 2021-12-09 18:15:33 -06:00
Validate FFI-safety warnings on naked functions Test that FFI-safety warnings don't get accidentally dropped on naked functions. The big picture is that if you implement a naked function with the Rust ABI you'll get a warning. Further, if you implement a naked function with a standardized ABI, but use non-FFI-safe types you will still get a warning. rust-lang/rfcs#2774 rust-lang/rfcs#2972 2021-08-03 16:43:21 -05:00			`#[naked]`
			`pub extern "C" fn naked(p: char) -> u128 {`
			//~^ WARN uses type `char`
			//~\| WARN uses type `u128`
Stabilize asm! and global_asm! They are also removed from the prelude as per the decision in https://github.com/rust-lang/rust/issues/87228. stdarch and compiler-builtins are updated to work with the new, stable asm! and global_asm! macros. 2021-12-09 18:15:33 -06:00			`unsafe {`
disallow `asm!` in `#[naked]` functions also disallow the `noreturn` option, and infer `naked_asm!` as `!` 2024-09-05 06:45:26 -05:00			`naked_asm!("");`
Stabilize asm! and global_asm! They are also removed from the prelude as per the decision in https://github.com/rust-lang/rust/issues/87228. stdarch and compiler-builtins are updated to work with the new, stable asm! and global_asm! macros. 2021-12-09 18:15:33 -06:00			`}`
Validate FFI-safety warnings on naked functions Test that FFI-safety warnings don't get accidentally dropped on naked functions. The big picture is that if you implement a naked function with the Rust ABI you'll get a warning. Further, if you implement a naked function with a standardized ABI, but use non-FFI-safe types you will still get a warning. rust-lang/rfcs#2774 rust-lang/rfcs#2972 2021-08-03 16:43:21 -05:00			`}`