This is a tracking issue for [RFC 2325][rfc], adding SIMD support to stable Rust. There's a number of components here, including: [rfc]: https://github.com/rust-lang/rfcs/pull/2325 * [`#[target_feature(enable = ...)]`](https://github.com/rust-lang/rust/issues/44839) * Names of accepted target features - [currently proposed](https://github.com/rust-lang/rfcs/blob/master/text/2325-stable-simd.md#the-target_feature-attribute) * [`#[cfg(target_feature = ...)]`](https://github.com/rust-lang/rust/issues/29717) * `is_target_feature_detected!` macro * `std::arch` naming and submodules The initial implementation of this is being added in https://github.com/rust-lang/rust/pull/48513 and the next steps would be: - [ ] Adjust documentation ([see instructions on forge][doc-guide]) - [ ] Stabilization PR ([see instructions on forge][stabilization-guide]) [stabilization-guide]: https://forge.rust-lang.org/stabilization-guide.html [doc-guide]: https://forge.rust-lang.org/stabilization-guide.html#updating-documentation --- ## Known issues * [ ] [`is_target_feature_detected!` takes different arguments that `#[target_feature]`](https://github.com/rust-lang-nursery/stdsimd/issues/348)
This is a tracking issue for RFC 2325, adding SIMD support to stable Rust. There's a number of components here, including:
#[target_feature(enable = ...)]#[cfg(target_feature = ...)]is_target_feature_detected!macrostd::archnaming and submodulesThe initial implementation of this is being added in #48513 and the next steps would be:
Known issues
is_target_feature_detected!takes different arguments that#[target_feature]