Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
onnx-runtime-ep-cpu
The CPU execution provider for the ORT 2.0 runtime (see docs/ORT2.md §4.4
and §54 Phase 1). It implements [onnx_runtime_ep_api::ExecutionProvider]
and hosts pure-Rust reference kernels for the Phase-1 op set (MatMul,
Add, Relu, Reshape, Transpose, Gather, LayerNormalization).
Backends: correctness baseline + SIMD fast path
The GEMM hot spot is served through [backend::CpuBackend] (docs/ORT2.md
§25.2). The default backend is a pure-Rust blocked, register-tiled,
rayon-parallelized f32 GEMM — the portable, offline correctness baseline that
compiles anywhere with no C++/FFI. On supported x86 hosts, the built-in
SimdX86 implementation provides the default fast path. Every backend lives behind the
[onnx_runtime_ep_api::Kernel] trait, so neither the EP contract nor the
session observes which one ran. See [kernels::matmul] for the hot spot.
unsafe
The default (Generic) path is unsafe-minimal: the only unsafe is the raw
device-buffer access the ep-api contract forces (aligned host
alloc/dealloc, memcpy, and strided element reads/writes), each isolated
and SAFETY-documented. The blocked rayon GEMM itself contains no unsafe;
all kernel arithmetic is safe Rust operating on
dense Vec<f32> buffers produced by the two audited accessors in [kernels].