Module device_ext 

Engine-layer extensions for rlx_driver::Device (plan #58).

is_available and available_devices consult the runtime’s backend registry + Cargo features, both of which are engine-layer concerns. Keeping them here preserves the one-way dep direction (driver doesn’t know about engine).

Functions

available_devices

Every variant currently available — Cargo-feature-gated or runtime-registered.

dispatch_report_for_device

Dispatch report for graph on device without mutating the graph (static common-ir probe).

dispatch_report_for_device_with_options

Like dispatch_report_for_device with explicit CompileOptions::kernel_dispatch.

first_unsupported_op

First op in graph that device cannot lower after rewrite, or None.

first_unsupported_op_with_options

Like first_unsupported_op with explicit CompileOptions::kernel_dispatch.

full_name

Pretty name with engine-known BLAS variant for the CPU device. Gives "CPU (Accelerate)" etc. when the relevant feature is on; falls back to the bare driver-side Device::name() when no BLAS feature is selected.

is_available

Check whether device has a compiled-in backend or has been registered by an external crate.

legalize_graph_for_device

Legalize graph for device using that backend’s claimed [OpKind] set.

legalize_graph_for_device_with_options

Like legalize_graph_for_device_with_report using CompileOptions::kernel_dispatch (and the same rewrite path as [Backend::compile]).

legalize_graph_for_device_with_report

Like legalize_graph_for_device but returns a [KernelDispatchReport] for tooling.

supports

Is op lowerable by the backend for device in this build?

supports_graph

Is every op in graph lowerable by device?

supports_graph_with_options

Like supports_graph with explicit CompileOptions::kernel_dispatch.