rust/tests/codegen-llvm/naked-fn/aligned.rs

//@ compile-flags: -C no-prepopulate-passes -Copt-level=0
//@ needs-asm-support
//@ ignore-arm no "ret" mnemonic
//@ ignore-wasm32 aligning functions is not currently supported on wasm (#143368)

#![crate_type = "lib"]
// FIXME(#82232, #143834): temporarily renamed to mitigate `#[align]` nameres ambiguity
#![feature(rustc_attrs)]
#![feature(fn_align)]

use std::arch::naked_asm;

// CHECK: .balign 16
// CHECK-LABEL: naked_empty:
#[rustc_align(16)]
#[no_mangle]
#[unsafe(naked)]
pub extern "C" fn naked_empty() {
    // CHECK: ret
    naked_asm!("ret")
}
add repr to the allowlist for naked functions, and test that it works 2024-08-22 19:48:39 +02:00			`//@ compile-flags: -C no-prepopulate-passes -Copt-level=0`
			`//@ needs-asm-support`
			`//@ ignore-arm no "ret" mnemonic`
Skip `align` tests on wasm 2025-07-06 18:10:52 -04:00			`//@ ignore-wasm32 aligning functions is not currently supported on wasm (#143368)`
add repr to the allowlist for naked functions, and test that it works 2024-08-22 19:48:39 +02:00
			`#![crate_type = "lib"]`
Mitigate `#[align]` name resolution ambiguity regression with a rename From `#[align]` -> `#[rustc_align]`. Attributes starting with `rustc` are always perma-unstable and feature-gated by `feature(rustc_attrs)`. See regression RUST-143834. For the underlying problem where even introducing new feature-gated unstable built-in attributes can break user code such as ```rs macro_rules! align { () => { /* .. */ }; } pub(crate) use align; // `use` here becomes ambiguous ``` refer to RUST-134963. Since the `#[align]` attribute is still feature-gated by `feature(fn_align)`, we can rename it as a mitigation. Note that `#[rustc_align]` will obviously mean that current unstable user code using `feature(fn_aling)` will need additionally `feature(rustc_attrs)`, but this is a short-term mitigation to buy time, and is expected to be changed to a better name with less collision potential. See <https://rust-lang.zulipchat.com/#narrow/channel/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202025-07-17/near/529290371> where mitigation options were considered. 2025-07-18 00:10:46 +08:00			// FIXME(#82232, #143834): temporarily renamed to mitigate `#[align]` nameres ambiguity
			`#![feature(rustc_attrs)]`
stabilize `naked_functions` 2024-12-18 22:05:27 +01:00			`#![feature(fn_align)]`
Mitigate `#[align]` name resolution ambiguity regression with a rename From `#[align]` -> `#[rustc_align]`. Attributes starting with `rustc` are always perma-unstable and feature-gated by `feature(rustc_attrs)`. See regression RUST-143834. For the underlying problem where even introducing new feature-gated unstable built-in attributes can break user code such as ```rs macro_rules! align { () => { /* .. */ }; } pub(crate) use align; // `use` here becomes ambiguous ``` refer to RUST-134963. Since the `#[align]` attribute is still feature-gated by `feature(fn_align)`, we can rename it as a mitigation. Note that `#[rustc_align]` will obviously mean that current unstable user code using `feature(fn_aling)` will need additionally `feature(rustc_attrs)`, but this is a short-term mitigation to buy time, and is expected to be changed to a better name with less collision potential. See <https://rust-lang.zulipchat.com/#narrow/channel/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202025-07-17/near/529290371> where mitigation options were considered. 2025-07-18 00:10:46 +08:00
disallow `asm!` in `#[naked]` functions also disallow the `noreturn` option, and infer `naked_asm!` as `!` 2024-09-05 13:45:26 +02:00			`use std::arch::naked_asm;`
add repr to the allowlist for naked functions, and test that it works 2024-08-22 19:48:39 +02:00
codegen `#[naked]` functions using `global_asm!` 2024-08-08 10:20:40 +02:00			`// CHECK: .balign 16`
			`// CHECK-LABEL: naked_empty:`
Mitigate `#[align]` name resolution ambiguity regression with a rename From `#[align]` -> `#[rustc_align]`. Attributes starting with `rustc` are always perma-unstable and feature-gated by `feature(rustc_attrs)`. See regression RUST-143834. For the underlying problem where even introducing new feature-gated unstable built-in attributes can break user code such as ```rs macro_rules! align { () => { /* .. */ }; } pub(crate) use align; // `use` here becomes ambiguous ``` refer to RUST-134963. Since the `#[align]` attribute is still feature-gated by `feature(fn_align)`, we can rename it as a mitigation. Note that `#[rustc_align]` will obviously mean that current unstable user code using `feature(fn_aling)` will need additionally `feature(rustc_attrs)`, but this is a short-term mitigation to buy time, and is expected to be changed to a better name with less collision potential. See <https://rust-lang.zulipchat.com/#narrow/channel/238009-t-compiler.2Fmeetings/topic/.5Bweekly.5D.202025-07-17/near/529290371> where mitigation options were considered. 2025-07-18 00:10:46 +08:00			`#[rustc_align(16)]`
add repr to the allowlist for naked functions, and test that it works 2024-08-22 19:48:39 +02:00			`#[no_mangle]`
Make `#[naked]` an unsafe attribute 2025-03-29 17:30:11 +01:00			`#[unsafe(naked)]`
			`pub extern "C" fn naked_empty() {`
codegen `#[naked]` functions using `global_asm!` 2024-08-08 10:20:40 +02:00			`// CHECK: ret`
Make `#[naked]` an unsafe attribute 2025-03-29 17:30:11 +01:00			`naked_asm!("ret")`
add repr to the allowlist for naked functions, and test that it works 2024-08-22 19:48:39 +02:00			`}`