Go to file
Jubilee a8385522ad
Merge portable-simd#195 - portable-simd:trait-ops
Generic `core::ops` for `Simd<T, _>`

In order to maintain type soundness, we need to be sure we only implement an operation for `Simd<T, _> where T: SimdElement`... and also valid for that operation in general. While we could do this purely parametrically, it is more sound to implement the operators directly for the base scalar type arguments and then use type parameters to extend the operators to the "higher order" operations.

This implements that strategy and cleans up `simd::ops` into a few submodules:
- assign.rs: `core::ops::*Assign`
- deref.rs:  `core::ops` impls which "deref" borrowed versions of the arguments
- unary.rs: encloses the logic for unary operators on `Simd`, as unary ops are much simpler

This is possible since everything need not be nested in a single maze of macros anymore. The result simplifies the logic and allows reasoning about what operators are valid based on the expressed trait bounds, and also reduces the size of the trait implementation output in rustdoc, for a huge win of 4 MB off the size of `struct.Simd.html`! This addresses a common user complaint, as the original was over 5.5 MB and capable of crashing browsers!

This also carries a fix for a type-inference-related breakage, by removing the autosplatting (vector + scalar binop) impls, as unfortunately the presence of autosplatting was capable of busting type inference. We will likely need to see results from a Crater run before we can understand how to re-land autosplatting.
2021-12-02 17:41:30 -08:00
.github Dynamically detect AVX512 in CI 2021-11-10 14:40:32 -08:00
crates Merge portable-simd#195 - portable-simd:trait-ops 2021-12-02 17:41:30 -08:00
.gitignore Add initial type implementations 2020-09-22 19:41:42 -04:00
beginners-guide.md Add to glossary: vectorize, scalar, vector register 2021-02-15 13:43:43 -08:00
Cargo.toml Add proptest float tests 2021-02-15 18:22:24 -05:00
CONTRIBUTING.md Update CONTRIBUTING.md for the fact that Travis is no longer used 2021-11-14 12:41:16 -05:00
LICENSE-APACHE Add licenses and update Cargo.toml 2020-10-01 23:42:10 -04:00
LICENSE-MIT Add licenses and update Cargo.toml 2020-10-01 23:42:10 -04:00
README.md Fix outdated workflow badge 2021-11-15 18:36:21 +05:30

The Rust standard library's portable SIMD API

Build Status

Code repository for the Portable SIMD Project Group. Please refer to CONTRIBUTING.md for our contributing guidelines.

The docs for this crate are published from the main branch. You can read them here.

If you have questions about SIMD, we have begun writing a guide. We can also be found on Zulip.

If you are interested in support for a specific architecture, you may want stdarch instead.

Hello World

Now we're gonna dip our toes into this world with a small SIMD "Hello, World!" example. Make sure your compiler is up to date and using nightly. We can do that by running

rustup update -- nightly

or by setting up rustup default nightly or else with cargo +nightly {build,test,run}. After updating, run

cargo new hellosimd

to create a new crate. Edit hellosimd/Cargo.toml to be

[package]
name = "hellosimd"
version = "0.1.0"
edition = "2018"
[dependencies]
core_simd = { git = "https://github.com/rust-lang/portable-simd" }

and finally write this in src/main.rs:

use core_simd::*;
fn main() {
    let a = f32x4::splat(10.0);
    let b = f32x4::from_array([1.0, 2.0, 3.0, 4.0]);
    println!("{:?}", a + b);
}

Explanation: We import all the bindings from the crate with the first line. Then, we construct our SIMD vectors with methods like splat or from_array. Finally, we can use operators on them like + and the appropriate SIMD instructions will be carried out. When we run cargo run you should get [11.0, 12.0, 13.0, 14.0].

Code Organization

Currently the crate is organized so that each element type is a file, and then the 64-bit, 128-bit, 256-bit, and 512-bit vectors using those types are contained in said file.

All types are then exported as a single, flat module.

Depending on the size of the primitive type, the number of lanes the vector will have varies. For example, 128-bit vectors have four f32 lanes and two f64 lanes.

The supported element types are as follows:

  • Floating Point: f32, f64
  • Signed Integers: i8, i16, i32, i64, i128, isize
  • Unsigned Integers: u8, u16, u32, u64, u128, usize
  • Masks: mask8, mask16, mask32, mask64, mask128, masksize

Floating point, signed integers, and unsigned integers are the primitive types you're already used to. The mask types are "truthy" values, but they use the number of bits in their name instead of just 1 bit like a normal bool uses.