Fearless SIMD v1.0 released: Rust crate takes unsafe out of SIMD code

Linebender has published fearless_simd v1.0, a Rust crate whose goal is to take unsafe out of SIMD — the technique of applying one instruction to several values at once. The announcement appeared on the project's blog on September 22, 2026, roughly eight years after the first prototype. The crate covers three levels of use: autovectorization and multiversioning, full portable SIMD abstractions, and safe access to hardware intrinsics.

Performance

A frequent criticism of portable SIMD abstractions is that they cost performance. For operations with platform-dependent edge cases, such as swizzles or floating-point maximum, the crate offers both a precise variant with identical results everywhere and a fast variant that returns platform-dependent results where those edge cases are not expected.

Algorithms can be written against the hardware's native vector width, or with fixed vector sizes when the algorithm needs them. The team also contributed improvements upstream to Rust and LLVM. Where portable operations are not enough, code can drop to platform intrinsics with no overhead for the parts that need them.

Safety

Other SIMD abstractions are full of unsafe code, the authors note; a keyword search can turn up several thousand blocks. Two small components keep fearless_simd free of ad-hoc unsafe: a kernel! macro that uses target feature 1.1 in the compiler to invoke most SIMD intrinsics safely, and a safe transmute module inspired by bytemuck and zerocopy, which replaces load and store intrinsics such as _mm_loadu_epi32 with one reusable wrapper. If those two self-contained blocks are memory-safe, the rest of the codebase is memory-safe by construction.

Ergonomics and stability

Function multiversioning has been awkward in Rust: earlier approaches required #[inline(always)] annotations and an understanding of their consequences, or added per-call overhead that hurts small functions. Version 1.0 ships alongside fearless_simd_macros v0.1, whose #[simd] attribute makes those decisions automatically; the manual route remains available.

The project promises three years of security updates for v1.0 and every later version, and sees a path to supporting the f16 type as well as the SVE and RISC-V vector extensions without API-breaking changes.

Adoption and the road to std::simd

Fearless SIMD is already a direct dependency of 30 crates and an indirect one for more than a thousand. The team says it would welcome a stabilized std::simd but argues that would not make the crate obsolete: the standard library implements only what has to live there, leaving multiversioning and hardware-width vectors to ecosystem crates. If std::simd stabilizes, the project plans to port to it, deleting custom code and gaining support for obscure platforms.