15 unstable releases

0.8.0 Dec 8, 2024
0.7.4 Mar 15, 2024
0.7.3 Aug 10, 2023
0.7.2 May 10, 2023
0.2.0 Nov 11, 2019

#22 in Hardware support

Download history 51966/week @ 2024-10-26 38423/week @ 2024-11-02 44956/week @ 2024-11-09 41821/week @ 2024-11-16 32634/week @ 2024-11-23 31813/week @ 2024-11-30 31287/week @ 2024-12-07 32140/week @ 2024-12-14 21580/week @ 2024-12-21 21121/week @ 2024-12-28 34724/week @ 2025-01-04 37292/week @ 2025-01-11 31867/week @ 2025-01-18 25810/week @ 2025-01-25 26203/week @ 2025-02-01 111274/week @ 2025-02-08

203,237 downloads per month
Used in 347 crates (18 directly)

MIT/Apache

19KB
134 lines

Multiversion

Crates.io Rust Documentation Rustc Version 1.61+ License

Function multiversioning attribute macros for Rust.

What is function multiversioning?

Many CPU architectures have a variety of instruction set extensions that provide additional functionality. Common examples are single instruction, multiple data (SIMD) extensions such as SSE and AVX on x86/x86-64 and NEON on ARM/AArch64. When available, these extended features can provide significant speed improvements to some functions. These optional features cannot be haphazardly compiled into programs--executing an unsupported instruction will result in a crash.

Function multiversioning is the practice of compiling multiple versions of a function with various features enabled and safely detecting which version to use at runtime.

Example

The multiversion macro compiles a function for multiple possible targets, and selects the optimal one at runtime:

use multiversion::multiversion;

#[multiversion(targets("x86_64+avx", "aarch64+neon"))]
fn square(x: &mut [f32]) {
    for v in x {
        *v *= *v;
    }
}

License

Multiversion is distributed under the terms of both the MIT license and the Apache License (Version 2.0).

See LICENSE-APACHE and LICENSE-MIT for details.

Dependencies

~240–680KB
~16K SLoC