Closed alvarozamora closed 2 years ago
@alvarozamora Unfortunately, I don't think this is even possible. The error stems from the root cause that the OpenCL device itself doesn't have double
support as reported by the OpenCL driver for that device. Unless, this changes there is no way double values data can be used on M1.
Just reiterating in another way, this is by no way a restriction on ArrayFire, it is just that Apple's M1 OpenCL driver isn't reporting double support - whether it has one or not is something I am not aware of it. Given that Apple stopped OpenCL support, this won't change in future too.
Another note: Any feature requests are better raised in the upstream project since this is just bindings project for arrayfire.
I am closing this one since this isn't possible in even in a remote future.
Description
I tried using these rust bindings for arrayfire for 3D FFTs on M1. They are blazing fast, but currently only support
Complex<f32>
's. Are there plans forComplex<f64>
's? Would love to use double precision.Currently, I get