Inline assembly

Support for inline assembly is provided via the asm! and global_asm! macros. It can be used to embed handwritten assembly in the assembly output generated by the compiler.

Support for inline assembly is stable on the following architectures:

• x86 and x86-64
• ARM
• AArch64 and Arm64EC
• RISC-V
• LoongArch
• s390x

The compiler will emit an error if asm! is used on an unsupported target.

Example

#![allow(unused)]
fn main() {
#[cfg(target_arch = "x86_64")] {
use std::arch::asm;

// Multiply x by 6 using shifts and adds
let mut x: u64 = 4;
unsafe {
    asm!(
        "mov {tmp}, {x}",
        "shl {tmp}, 1",
        "shl {x}, 2",
        "add {x}, {tmp}",
        x = inout(reg) x,
        tmp = out(reg) _,
    );
}
assert_eq!(x, 4 * 6);
}
}

Syntax

The following ABNF specifies the general syntax:

format_string := STRING_LITERAL / RAW_STRING_LITERAL
dir_spec := "in" / "out" / "lateout" / "inout" / "inlateout"
reg_spec := <register class> / "\"" <explicit register> "\""
operand_expr := expr / "_" / expr "=>" expr / expr "=>" "_"
reg_operand := [ident "="] dir_spec "(" reg_spec ")" operand_expr / sym <path> / const <expr>
clobber_abi := "clobber_abi(" <abi> *("," <abi>) [","] ")"
option := "pure" / "nomem" / "readonly" / "preserves_flags" / "noreturn" / "nostack" / "att_syntax" / "raw"
options := "options(" option *("," option) [","] ")"
operand := reg_operand / clobber_abi / options
asm := "asm!(" format_string *("," format_string) *("," operand) [","] ")"
global_asm := "global_asm!(" format_string *("," format_string) *("," operand) [","] ")"

Scope

Inline assembly can be used in one of two ways.

With the asm! macro, the assembly code is emitted in a function scope and integrated into the compiler-generated assembly code of a function. This assembly code must obey strict rules to avoid undefined behavior. Note that in some cases the compiler may choose to emit the assembly code as a separate function and generate a call to it.

With the global_asm! macro, the assembly code is emitted in a global scope, outside a function. This can be used to hand-write entire functions using assembly code, and generally provides much more freedom to use arbitrary registers and assembler directives.

Template string arguments

The assembler template uses the same syntax as format strings (i.e. placeholders are specified by curly braces).

The corresponding arguments are accessed in order, by index, or by name.

However, implicit named arguments (introduced by RFC #2795) are not supported.

An asm! invocation may have one or more template string arguments; an asm! with multiple template string arguments is treated as if all the strings were concatenated with a \n between them. The expected usage is for each template string argument to correspond to a line of assembly code.

All template string arguments must appear before any other arguments.

As with format strings, positional arguments must appear before named arguments and explicit register operands.

Explicit register operands cannot be used by placeholders in the template string.

All other named and positional operands must appear at least once in the template string, otherwise a compiler error is generated.

The exact assembly code syntax is target-specific and opaque to the compiler except for the way operands are substituted into the template string to form the code passed to the assembler.

Currently, all supported targets follow the assembly code syntax used by LLVM’s internal assembler which usually corresponds to that of the GNU assembler (GAS). On x86, the .intel_syntax noprefix mode of GAS is used by default. On ARM, the .syntax unified mode is used. These targets impose an additional restriction on the assembly code: any assembler state (e.g. the current section which can be changed with .section) must be restored to its original value at the end of the asm string. Assembly code that does not conform to the GAS syntax will result in assembler-specific behavior. Further constraints on the directives used by inline assembly are indicated by Directives Support.

Operand type

Several types of operands are supported:

• in(<reg>) <expr>
  • <reg> can refer to a register class or an explicit register. The allocated register name is substituted into the asm template string.
  • The allocated register will contain the value of <expr> at the start of the asm code.
  • The allocated register must contain the same value at the end of the asm code (except if a lateout is allocated to the same register).

• out(<reg>) <expr>
  • <reg> can refer to a register class or an explicit register. The allocated register name is substituted into the asm template string.
  • The allocated register will contain an undefined value at the start of the asm code.
  • <expr> must be a (possibly uninitialized) place expression, to which the contents of the allocated register are written at the end of the asm code.
  • An underscore (_) may be specified instead of an expression, which will cause the contents of the register to be discarded at the end of the asm code (effectively acting as a clobber).

• lateout(<reg>) <expr>
  • Identical to out except that the register allocator can reuse a register allocated to an in.
  • You should only write to the register after all inputs are read, otherwise you may clobber an input.

• inout(<reg>) <expr>
  • <reg> can refer to a register class or an explicit register. The allocated register name is substituted into the asm template string.
  • The allocated register will contain the value of <expr> at the start of the asm code.
  • <expr> must be a mutable initialized place expression, to which the contents of the allocated register are written at the end of the asm code.

• inout(<reg>) <in expr> => <out expr>
  • Same as inout except that the initial value of the register is taken from the value of <in expr>.
  • <out expr> must be a (possibly uninitialized) place expression, to which the contents of the allocated register are written at the end of the asm code.
  • An underscore (_) may be specified instead of an expression for <out expr>, which will cause the contents of the register to be discarded at the end of the asm code (effectively acting as a clobber).
  • <in expr> and <out expr> may have different types.

• inlateout(<reg>) <expr> / inlateout(<reg>) <in expr> => <out expr>
  • Identical to inout except that the register allocator can reuse a register allocated to an in (this can happen if the compiler knows the in has the same initial value as the inlateout).
  • You should only write to the register after all inputs are read, otherwise you may clobber an input.

• sym <path>
  • <path> must refer to a fn or static.
  • A mangled symbol name referring to the item is substituted into the asm template string.
  • The substituted string does not include any modifiers (e.g. GOT, PLT, relocations, etc).
  • <path> is allowed to point to a #[thread_local] static, in which case the asm code can combine the symbol with relocations (e.g. @plt, @TPOFF) to read from thread-local data.
• const <expr>
  • <expr> must be an integer constant expression. This expression follows the same rules as inline const blocks.
  • The type of the expression may be any integer type, but defaults to i32 just like integer literals.
  • The value of the expression is formatted as a string and substituted directly into the asm template string.

Operand expressions are evaluated from left to right, just like function call arguments. After the asm! has executed, outputs are written to in left to right order. This is significant if two outputs point to the same place: that place will contain the value of the rightmost output.

Since global_asm! exists outside a function, it can only use sym and const operands.

Register operands

Input and output operands can be specified either as an explicit register or as a register class from which the register allocator can select a register. Explicit registers are specified as string literals (e.g. "eax") while register classes are specified as identifiers (e.g. reg).

Note that explicit registers treat register aliases (e.g. r14 vs lr on ARM) and smaller views of a register (e.g. eax vs rax) as equivalent to the base register.

It is a compile-time error to use the same explicit register for two input operands or two output operands.

Additionally, it is also a compile-time error to use overlapping registers (e.g. ARM VFP) in input operands or in output operands.

Only the following types are allowed as operands for inline assembly:

• Integers (signed and unsigned)
• Floating-point numbers
• Pointers (thin only)
• Function pointers
• SIMD vectors (structs defined with #[repr(simd)] and which implement Copy). This includes architecture-specific vector types defined in std::arch such as __m128 (x86) or int8x16_t (ARM).

Here is the list of currently supported register classes:

Notes:

• On x86 we treat reg_byte differently from reg because the compiler can allocate al and ah separately whereas reg reserves the whole register.
• On x86-64 the high byte registers (e.g. ah) are not available in the reg_byte register class.
• Some register classes are marked as “Only clobbers” which means that registers in these classes cannot be used for inputs or outputs, only clobbers of the form out(<explicit register>) _ or lateout(<explicit register>) _.

Each register class has constraints on which value types they can be used with. This is necessary because the way a value is loaded into a register depends on its type. For example, on big-endian systems, loading a i32x4 and a i8x16 into a SIMD register may result in different register contents even if the byte-wise memory representation of both values is identical. The availability of supported types for a particular register class may depend on what target features are currently enabled.

Note: For the purposes of the above table pointers, function pointers and isize/usize are treated as the equivalent integer type (i16/i32/i64 depending on the target).

If a value is of a smaller size than the register it is allocated in then the upper bits of that register will have an undefined value for inputs and will be ignored for outputs. The only exception is the freg register class on RISC-V where f32 values are NaN-boxed in a f64 as required by the RISC-V architecture.

When separate input and output expressions are specified for an inout operand, both expressions must have the same type. The only exception is if both operands are pointers or integers, in which case they are only required to have the same size. This restriction exists because the register allocators in LLVM and GCC sometimes cannot handle tied operands with different types.

Register names

Some registers have multiple names. These are all treated by the compiler as identical to the base register name. Here is the list of all supported register aliases:

Some registers cannot be used for input or output operands:

The frame pointer and base pointer registers are reserved for internal use by LLVM. While asm! statements cannot explicitly specify the use of reserved registers, in some cases LLVM will allocate one of these reserved registers for reg operands. Assembly code making use of reserved registers should be careful since reg operands may use the same registers.

Template modifiers

The placeholders can be augmented by modifiers which are specified after the : in the curly braces. These modifiers do not affect register allocation, but change the way operands are formatted when inserted into the template string.

Only one modifier is allowed per template placeholder.

The supported modifiers are a subset of LLVM’s (and GCC’s) asm template argument modifiers, but do not use the same letter codes.

Notes:

• on ARM e / f: this prints the low or high doubleword register name of a NEON quad (128-bit) register.
• on x86: our behavior for reg with no modifiers differs from what GCC does. GCC will infer the modifier based on the operand value type, while we default to the full register size.
• on x86 xmm_reg: the x, t and g LLVM modifiers are not yet implemented in LLVM (they are supported by GCC only), but this should be a simple change.

As stated in the previous section, passing an input value smaller than the register width will result in the upper bits of the register containing undefined values. This is not a problem if the inline asm only accesses the lower bits of the register, which can be done by using a template modifier to use a subregister name in the asm code (e.g. ax instead of rax). Since this an easy pitfall, the compiler will suggest a template modifier to use where appropriate given the input type. If all references to an operand already have modifiers then the warning is suppressed for that operand.

ABI clobbers

The clobber_abi keyword can be used to apply a default set of clobbers to an asm! block. This will automatically insert the necessary clobber constraints as needed for calling a function with a particular calling convention: if the calling convention does not fully preserve the value of a register across a call then lateout("...") _ is implicitly added to the operands list (where the ... is replaced by the register’s name).

clobber_abi may be specified any number of times. It will insert a clobber for all unique registers in the union of all specified calling conventions.

Generic register class outputs are disallowed by the compiler when clobber_abi is used: all outputs must specify an explicit register.

Explicit register outputs have precedence over the implicit clobbers inserted by clobber_abi: a clobber will only be inserted for a register if that register is not used as an output.

The following ABIs can be used with clobber_abi:

Notes:

• On AArch64 x18 only included in the clobber list if it is not considered as a reserved register on the target.
• On RISC-V x[16-17] and x[28-31] only included in the clobber list if they are not considered as reserved registers on the target.

The list of clobbered registers for each ABI is updated in rustc as architectures gain new registers: this ensures that asm! clobbers will continue to be correct when LLVM starts using these new registers in its generated code.

Options

Flags are used to further influence the behavior of the inline assembly block. Currently the following options are defined:

• pure: The asm! block has no side effects, must eventually return, and its outputs depend only on its direct inputs (i.e. the values themselves, not what they point to) or values read from memory (unless the nomem options is also set). This allows the compiler to execute the asm! block fewer times than specified in the program (e.g. by hoisting it out of a loop) or even eliminate it entirely if the outputs are not used. The pure option must be combined with either the nomem or readonly options, otherwise a compile-time error is emitted.

• nomem: The asm! block does not read from or write to any memory accessible outside of the asm! block. This allows the compiler to cache the values of modified global variables in registers across the asm! block since it knows that they are not read or written to by the asm!. The compiler also assumes that this asm! block does not perform any kind of synchronization with other threads, e.g. via fences.

• readonly: The asm! block does not write to any memory accessible outside of the asm! block. This allows the compiler to cache the values of unmodified global variables in registers across the asm! block since it knows that they are not written to by the asm!. The compiler also assumes that this asm! block does not perform any kind of synchronization with other threads, e.g. via fences.

• preserves_flags: The asm! block does not modify the flags register (defined in the rules below). This allows the compiler to avoid recomputing the condition flags after the asm! block.

• noreturn: The asm! block never returns, and its return type is defined as ! (never). Behavior is undefined if execution falls through past the end of the asm code. A noreturn asm block behaves just like a function which doesn’t return; notably, local variables in scope are not dropped before it is invoked.

• nostack: The asm! block does not push data to the stack, or write to the stack red-zone (if supported by the target). If this option is not used then the stack pointer is guaranteed to be suitably aligned (according to the target ABI) for a function call.

• att_syntax: This option is only valid on x86, and causes the assembler to use the .att_syntax prefix mode of the GNU assembler. Register operands are substituted in with a leading %.

• raw: This causes the template string to be parsed as a raw assembly string, with no special handling for { and }. This is primarily useful when including raw assembly code from an external file using include_str!.

The compiler performs some additional checks on options:

• The nomem and readonly options are mutually exclusive: it is a compile-time error to specify both.

• It is a compile-time error to specify pure on an asm block with no outputs or only discarded outputs (_).

• It is a compile-time error to specify noreturn on an asm block with outputs.

global_asm! only supports the att_syntax and raw options. The remaining options are not meaningful for global-scope inline assembly

Rules for inline assembly

To avoid undefined behavior, these rules must be followed when using function-scope inline assembly (asm!):

• Any registers not specified as inputs will contain an undefined value on entry to the asm block.
  • An “undefined value” in the context of inline assembly means that the register can (non-deterministically) have any one of the possible values allowed by the architecture. Notably it is not the same as an LLVM undef which can have a different value every time you read it (since such a concept does not exist in assembly code).

• Any registers not specified as outputs must have the same value upon exiting the asm block as they had on entry, otherwise behavior is undefined.
  • This only applies to registers which can be specified as an input or output. Other registers follow target-specific rules.
  • Note that a lateout may be allocated to the same register as an in, in which case this rule does not apply. Code should not rely on this however since it depends on the results of register allocation.

• Behavior is undefined if execution unwinds out of an asm block.
  • This also applies if the assembly code calls a function which then unwinds.

• The set of memory locations that assembly code is allowed to read and write are the same as those allowed for an FFI function.
  • Refer to the unsafe code guidelines for the exact rules.
  • If the readonly option is set, then only memory reads are allowed.
  • If the nomem option is set then no reads or writes to memory are allowed.
  • These rules do not apply to memory which is private to the asm code, such as stack space allocated within the asm block.

• The compiler cannot assume that the instructions in the asm are the ones that will actually end up executed.
  • This effectively means that the compiler must treat the asm! as a black box and only take the interface specification into account, not the instructions themselves.
  • Runtime code patching is allowed, via target-specific mechanisms.
  • However there is no guarantee that each asm! directly corresponds to a single instance of instructions in the object file: the compiler is free to duplicate or deduplicate asm! blocks.

• Unless the nostack option is set, asm code is allowed to use stack space below the stack pointer.
  • On entry to the asm block the stack pointer is guaranteed to be suitably aligned (according to the target ABI) for a function call.
  • You are responsible for making sure you don’t overflow the stack (e.g. use stack probing to ensure you hit a guard page).
  • You should adjust the stack pointer when allocating stack memory as required by the target ABI.
  • The stack pointer must be restored to its original value before leaving the asm block.

• If the noreturn option is set then behavior is undefined if execution falls through to the end of the asm block.

• If the pure option is set then behavior is undefined if the asm! has side-effects other than its direct outputs. Behavior is also undefined if two executions of the asm! code with the same inputs result in different outputs.
  • When used with the nomem option, “inputs” are just the direct inputs of the asm!.
  • When used with the readonly option, “inputs” comprise the direct inputs of the asm! and any memory that the asm! block is allowed to read.

• These flags registers must be restored upon exiting the asm block if the preserves_flags option is set:
  • x86
    • Status flags in EFLAGS (CF, PF, AF, ZF, SF, OF).
    • Floating-point status word (all).
    • Floating-point exception flags in MXCSR (PE, UE, OE, ZE, DE, IE).
  • ARM
    • Condition flags in CPSR (N, Z, C, V)
    • Saturation flag in CPSR (Q)
    • Greater than or equal flags in CPSR (GE).
    • Condition flags in FPSCR (N, Z, C, V)
    • Saturation flag in FPSCR (QC)
    • Floating-point exception flags in FPSCR (IDC, IXC, UFC, OFC, DZC, IOC).
  • AArch64 and Arm64EC
    • Condition flags (NZCV register).
    • Floating-point status (FPSR register).
  • RISC-V
    • Floating-point exception flags in fcsr (fflags).
    • Vector extension state (vtype, vl, vcsr).
  • LoongArch
    • Floating-point condition flags in $fcc[0-7].
  • s390x
    • The condition code register cc.

• On x86, the direction flag (DF in EFLAGS) is clear on entry to an asm block and must be clear on exit.
  • Behavior is undefined if the direction flag is set on exiting an asm block.

• On x86, the x87 floating-point register stack must remain unchanged unless all of the st([0-7]) registers have been marked as clobbered with out("st(0)") _, out("st(1)") _, ....
  • If all x87 registers are clobbered then the x87 register stack is guaranteed to be empty upon entering an asm block. Assembly code must ensure that the x87 register stack is also empty when exiting the asm block.

• On arm64ec, call checkers with appropriate thunks are mandatory when calling functions.

• The requirement of restoring the stack pointer and non-output registers to their original value only applies when exiting an asm! block.
  • This means that asm! blocks that never return (even if not marked noreturn) don’t need to preserve these registers.
  • When returning to a different asm! block than you entered (e.g. for context switching), these registers must contain the value they had upon entering the asm! block that you are exiting.
    • You cannot exit an asm! block that has not been entered. Neither can you exit an asm! block that has already been exited (without first entering it again).
    • You are responsible for switching any target-specific state (e.g. thread-local storage, stack bounds).
    • You cannot jump from an address in one asm! block to an address in another, even within the same function or block, without treating their contexts as potentially different and requiring context switching. You cannot assume that any particular value in those contexts (e.g. current stack pointer or temporary values below the stack pointer) will remain unchanged between the two asm! blocks.
    • The set of memory locations that you may access is the intersection of those allowed by the asm! blocks you entered and exited.

• You cannot assume that two asm! blocks adjacent in source code, even without any other code between them, will end up in successive addresses in the binary without any other instructions between them.

• You cannot assume that an asm! block will appear exactly once in the output binary. The compiler is allowed to instantiate multiple copies of the asm! block, for example when the function containing it is inlined in multiple places.

• On x86, inline assembly must not end with an instruction prefix (such as LOCK) that would apply to instructions generated by the compiler.
  • The compiler is currently unable to detect this due to the way inline assembly is compiled, but may catch and reject this in the future.

Note: As a general rule, the flags covered by preserves_flags are those which are not preserved when performing a function call.

Correctness and Validity

In addition to all of the previous rules, the string argument to asm! must ultimately become— after all other arguments are evaluated, formatting is performed, and operands are translated— assembly that is both syntactically correct and semantically valid for the target architecture. The formatting rules allow the compiler to generate assembly with correct syntax. Rules concerning operands permit valid translation of Rust operands into and out of asm!. Adherence to these rules is necessary, but not sufficient, for the final expanded assembly to be both correct and valid. For instance:

• arguments may be placed in positions which are syntactically incorrect after formatting
• an instruction may be correctly written, but given architecturally invalid operands
• an architecturally unspecified instruction may be assembled into unspecified code
• a set of instructions, each correct and valid, may cause undefined behavior if placed in immediate succession

As a result, these rules are non-exhaustive. The compiler is not required to check the correctness and validity of the initial string nor the final assembly that is generated. The assembler may check for correctness and validity but is not required to do so. When using asm!, a typographical error may be sufficient to make a program unsound, and the rules for assembly may include thousands of pages of architectural reference manuals. Programmers should exercise appropriate care, as invoking this unsafe capability comes with assuming the responsibility of not violating rules of both the compiler or the architecture.

Directives Support

Inline assembly supports a subset of the directives supported by both GNU AS and LLVM’s internal assembler, given as follows. The result of using other directives is assembler-specific (and may cause an error, or may be accepted as-is).

If inline assembly includes any “stateful” directive that modifies how subsequent assembly is processed, the block must undo the effects of any such directives before the inline assembly ends.

The following directives are guaranteed to be supported by the assembler:

• .2byte
• .4byte
• .8byte
• .align
• .alt_entry
• .ascii
• .asciz
• .balign
• .balignl
• .balignw
• .bss
• .byte
• .comm
• .data
• .def
• .double
• .endef
• .equ
• .equiv
• .eqv
• .fill
• .float
• .global
• .globl
• .inst
• .insn
• .lcomm
• .long
• .octa
• .option
• .p2align
• .popsection
• .private_extern
• .pushsection
• .quad
• .scl
• .section
• .set
• .short
• .size
• .skip
• .sleb128
• .space
• .string
• .text
• .type
• .uleb128
• .word

Target Specific Directive Support

Dwarf Unwinding

The following directives are supported on ELF targets that support DWARF unwind info:

• .cfi_adjust_cfa_offset
• .cfi_def_cfa
• .cfi_def_cfa_offset
• .cfi_def_cfa_register
• .cfi_endproc
• .cfi_escape
• .cfi_lsda
• .cfi_offset
• .cfi_personality
• .cfi_register
• .cfi_rel_offset
• .cfi_remember_state
• .cfi_restore
• .cfi_restore_state
• .cfi_return_column
• .cfi_same_value
• .cfi_sections
• .cfi_signal_frame
• .cfi_startproc
• .cfi_undefined
• .cfi_window_save

Structured Exception Handling

On targets with structured exception Handling, the following additional directives are guaranteed to be supported:

• .seh_endproc
• .seh_endprologue
• .seh_proc
• .seh_pushreg
• .seh_savereg
• .seh_setframe
• .seh_stackalloc

x86 (32-bit and 64-bit)

On x86 targets, both 32-bit and 64-bit, the following additional directives are guaranteed to be supported:

• .nops
• .code16
• .code32
• .code64

Use of .code16, .code32, and .code64 directives are only supported if the state is reset to the default before exiting the assembly block. 32-bit x86 uses .code32 by default, and x86_64 uses .code64 by default.

ARM (32-bit)

On ARM, the following additional directives are guaranteed to be supported:

• .even
• .fnstart
• .fnend
• .save
• .movsp
• .code
• .thumb
• .thumb_func