630577cb98
Re-vendors wide 0.7 + safe_arch, restores the upstream simd-stable wiring in rapier3d/parry3d manifests and the cfg-simd source, and drops the added 'stripped build does not support SIMD' guards (upstream's simd-vs-enhanced-determinism exclusivity guard kept). Interleaved single-thread retest (min of 4): SIMD buys rapier 1.8-2.2x; box3d vs rapier-simd is now near parity — large_pyramid 1579 vs 1638 ms, joint_grid 957 vs 1008 ms (box3d ahead), many_pyramids 2389 vs 1970 ms (rapier ahead). box3d README grid updated with the honest three-column table; box3d keeps cross-arch determinism + zero deps at that speed. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
17 lines
853 B
Markdown
17 lines
853 B
Markdown
[](https://opensource.org/licenses/Zlib)
|
|
|
|
[](https://crates.io/crates/wide)
|
|
[](https://docs.rs/wide/)
|
|
|
|
# wide
|
|
|
|
A crate to help you go wide.
|
|
|
|
Specifically, this has portable "wide" data types that do their best to be SIMD when possible.
|
|
|
|
On `x86`, `x86_64`, `wasm32` and `aarch64 neon` this is done with explicit
|
|
intrinsic usage (via [safe_arch](https://docs.rs/safe_arch)), and on other
|
|
architectures this is done by carefully writing functions so that LLVM hopefully
|
|
does the right thing. When Rust stabilizes more explicit intrinsics then they
|
|
can go into `safe_arch` and then they can get used here.
|
|
|