safe_arch
| Crates.io | safe_arch |
| lib.rs | safe_arch |
| version | |
| source | src |
| created_at | 2020-04-29 02:53:57.692152+00 |
| updated_at | 2024-12-21 14:53:27.25882+00 |
| description | Crate that exposes `core::arch` safely via `#[cfg()]`. |
| homepage | |
| repository | https://github.com/Lokathor/safe_arch |
| max_upload_size | |
| id | 235203 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
Lokathor (Lokathor)
documentation
README
Docs.rs
safe_arch
Exposes arch-specific intrinsics as safe function.
- SIMD types are newtype'd (with a
pubfield) and given appropriate trait impls such asFrom,Into,Default, etc. - Each intrinsic gets either a function or macro so that you can safely use it
as directly as possible.
- Functions are used when all arguments are runtime arguments.
- Macros are used when one of the arguments must be a compile time constant, because Rust doesn't let you "pass through" compile time constants.
- There's hundreds and hundreds of intrinsics, so the names of functions and
macros tend to be very long and specific because there's often many similar
ways to do nearly the same thing.
- This crate isn't really intended for "everyday users". It is intended to be an "unopinionated" middle layer crate that just provides the safety. Higher level abstractions should mostly come from some other crate that wraps over this crate.
All function and macro availability is done purely at compile time via
#[cfg()] attributes on the various modules. If a CPU feature isn't enabled for
the build then those functions or macros won't be available. If you'd like to
determine what CPU features are available at runtime and then call different
code accordingly, this crate is not for you.
See the crate docs for more details.
Additional Resources
- Intel Intrinsics Guide
- Raw Xml v3.5.2 and you can check their release notes to see if a later version has been put out since this readme file was last updated.