14 releases

0.7.4 Mar 15, 2024
0.7.3 Aug 10, 2023
0.7.2 May 10, 2023
0.7.1 Dec 23, 2022
0.2.0 Nov 11, 2019

#19 in Hardware support

Download history 21952/week @ 2023-12-05 24999/week @ 2023-12-12 21488/week @ 2023-12-19 15936/week @ 2023-12-26 27146/week @ 2024-01-02 28143/week @ 2024-01-09 28890/week @ 2024-01-16 26565/week @ 2024-01-23 27019/week @ 2024-01-30 27101/week @ 2024-02-06 29430/week @ 2024-02-13 28075/week @ 2024-02-20 22989/week @ 2024-02-27 25640/week @ 2024-03-05 25939/week @ 2024-03-12 24102/week @ 2024-03-19

103,133 downloads per month
Used in 220 crates (15 directly)

MIT/Apache

19KB
139 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

~1.5MB
~35K SLoC