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 32028/week @ 2024-11-25 32374/week @ 2024-12-02 30616/week @ 2024-12-09 31266/week @ 2024-12-16 21746/week @ 2024-12-23 21957/week @ 2024-12-30 35137/week @ 2025-01-06 36465/week @ 2025-01-13 30872/week @ 2025-01-20 24671/week @ 2025-01-27 27069/week @ 2025-02-03 120324/week @ 2025-02-10 119404/week @ 2025-02-17 143585/week @ 2025-02-24 151551/week @ 2025-03-03 139814/week @ 2025-03-10

557,626 downloads per month
Used in 339 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