8ca47d7ae4
Like I previously did for `reverse`, this leaves it to LLVM to pick how to vectorize it, since it can know better the chunk size to use, compared to the "32 bytes always" approach we currently have. It does still need logic to type-erase where appropriate, though, as while LLVM is now smart enough to vectorize over slices of things like `[u8; 4]`, it fails to do so over slices of `[u8; 3]`. As a bonus, this also means one no longer gets the spurious `memcpy`(s?) at the end up swapping a slice of `__m256`s: <https://rust.godbolt.org/z/joofr4v8Y> |
||
|---|---|---|
| .. | ||
| ascii | ||
| char | ||
| hash | ||
| num | ||
| str | ||
| any.rs | ||
| ascii.rs | ||
| fmt.rs | ||
| iter.rs | ||
| lib.rs | ||
| ops.rs | ||
| pattern.rs | ||
| slice.rs | ||
| str.rs | ||