Email me

Clippy lints / Suspicious

Clippy lint · Suspicious · checked with Clippy 0.1.99

clippy::pointers_in_nomem_asm_block: passing pointers to nomem asm block

What it meansChecks if any pointer is being passed to an asm! block with nomem option. It is in the suspicious group and warns by default.

What you see

warning: passing pointers to nomem asm block
 --> main.rs:4:48
  |
4 |     unsafe { core::arch::asm!("mov [{p}], 42", p = in(reg) p, options(nomem, nostack)); }
  |                                                ^^^^^^^^^^^^^
  |
  = note: `nomem` means that no memory write or read happens inside the asm! block
  = note: if this is intentional and no pointers are read or written to, consider allowing the lint
  = help: for further information visit https://rust-lang.github.io/rust-clippy/stable/index.html#pointers_in_nomem_asm_block
  = note: `#[warn(clippy::pointers_in_nomem_asm_block)]` on by default

Real output of Clippy 0.1.99 (Rust 1.99) on the example below. Names and line numbers in yours will differ.

Does it matter?

nomem forbids any reads or writes to memory and passing a pointer suggests that either of those will happen.

Code that is most likely wrong or useless. Warns by default.

How to fix it

Clippy does not fix this one automatically. Change the code by hand:

Flagged

fn f(p: *mut u32) {
    unsafe { core::arch::asm!("mov [{p}], 42", p = in(reg) p, options(nomem, nostack)); }
}

Write this instead

fn f(p: *mut u32) {
    unsafe { core::arch::asm!("mov [{p}], 42", p = in(reg) p, options(nostack)); }
}

Turn it off, or on

Allow it where it does not fit your code, as narrowly as you can:

On one item

#[allow(clippy::pointers_in_nomem_asm_block)]
fn my_function() { /* ... */ }

Whole crate (Cargo.toml)

[lints.clippy]
pointers_in_nomem_asm_block = "allow"

One run

cargo clippy -- -A clippy::pointers-in-nomem-asm-block

The [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.

Suspiciousgroup
warndefault level
nofixed by cargo clippy --fix
1.81.0added in Rust

Clippy's own documentation

What it does

Checks if any pointer is being passed to an asm! block with nomem option.

Why is this bad?

nomem forbids any reads or writes to memory and passing a pointer suggests that either of those will happen.

Example

fn f(p: *mut u32) {
    unsafe { core::arch::asm!("mov [{p}], 42", p = in(reg) p, options(nomem, nostack)); }
}

Use instead:

fn f(p: *mut u32) {
    unsafe { core::arch::asm!("mov [{p}], 42", p = in(reg) p, options(nostack)); }
}

From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.

Related lints

All 847 Clippy lints · Rust compiler errors · Cargo.toml checker

Up next

Related lintclippy::octal_escapesoctal-looking escape in a literalRead it next →

Did this answer your question?

Get the receipts by email.

What my AI agents tried this week, with the real numbers: what worked, what flopped, what made money. One email when there is something worth reading.

No spam, never sold. Every email has a one-click unsubscribe.

Popular in the shop

All 124 tools →

Browse: Bundles and kitsHome, family and schoolMoney and businessAI toolsSports and fitnessMaking and hobbiesFood and drinkIndie dev and launchTrading and quant

Free: Landing page teardown iPhone app cost calculator LLM API cost calculator Paid online: $49 Launch Check App builds Articles FAQ