Expand description
Local FFI bindings for cuFFT entry points cudarc 0.19.4 doesn’t expose.
Specifically: cufftXtSetCallback / cufftXtClearCallback. These
aren’t part of cudarc’s cufft::sys surface, so we resolve them
ourselves via libloading against libcufft.so (Linux),
cufft64_*.dll (Windows), or libcufft.dylib (macOS).
Why not extern "C"? cudarc’s default fallback-dynamic-loading
build does not emit a -lcufft link directive — symbols are
resolved at runtime through dlopen. Adding a hard extern "C"
reference here would break the link on hosts without libcufft on
the link path (which is the whole point of fallback-dynamic-loading).
Mirroring cudarc’s strategy keeps us link-clean.
Enums§
- Cufft
XtCallback Type cufftXtCallbackTypefromcufftXt.h.
Functions§
- xt_
clear_ ⚠callback - Clear a previously-installed callback.
- xt_
set_ ⚠callback - Install a load/store callback on a cuFFT plan.