Crate ferrox_cuda 

ferrox-cuda: hardware capability detection (always compiled, always tested) plus an optional, feature-gated CUDA execution path.

Build without any GPU support (the default): cargo build -p ferrox-cuda. Build with the CUDA scaffolding included: cargo build -p ferrox-cuda --features cuda.

The cuda feature compiles cleanly in this development sandbox (which has neither a CUDA toolkit nor a GPU) because cudarc is configured for dynamic loading – the driver and NVRTC libraries are dlopen’d at runtime, not linked at build time. That means “this crate compiles with --features cuda” is a true, checked fact. It does not mean the CUDA kernels in gpu.rs have ever executed successfully; see that module’s docs for exactly what has and has not been verified.

Re-exports

pub use capability::HardwareProfile;

pub use capability::SimdCaps;

Modules

capability

Runtime hardware capability detection: probe once, report a plain struct, and let every performance-relevant decision (thread pool width, SIMD kernel selection, GPU residency) derive from the detected machine rather than being hardcoded. Ferrox today only has a CPU execution path, so HardwareProfile::detect() is honest about that: the CUDA fields are always populated (zero / false / None) unless built with --features cuda, and even then they report exactly what ferrox-cuda’s device probe finds, no more.