-
Notifications
You must be signed in to change notification settings - Fork 192
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenCL 2.0 / SVM support? #217
Comments
clFFT is under maintenance mode. So no active development. AMD encourage developer switch to ROCM using rocFFT: https://github.com/ROCmSoftwarePlatform/rocFFT |
Thanks for clarification. |
use rocFFT no hcFFT. We recommend user to use rocFFT but not say goodbye to clFFT yet. |
clFFT can run on rocm as well; we are pointing everyone to use the rocm stack. |
I do not really understand why AMD seems to be turning it's back on OpenCL. It was great to have platform independent HPC libraries like clFFT and clBLAS and I wished there were more. Using rocFFT I have to compile different binaries for AMD and Nvidia (what about CPUs or Intel GPUs?). If now all vendors go back to platform specific solutions probably most developers will turn to the most evolved solution, which unfortunately is CUDA. |
@TillAlex I agree that OpenCL is great for portability for many of our users; but a lot of what we do is dictated by market demands and adoptions, and unfortunately opencl has not had that wide traction. Please note we still try to support clFFT and opencl runs on rocm stack. |
you can run rocFFT on Nvidia GPU. rocFFT is written in HIP. HIP can run on NVIDIA GPU. |
Thanks for your replies. To make in more specific: We plan heavy signal processing (fft, filtering, clustering, ...) on a embedded Ryzen V1000 and need to utilize the APU efficiently. HIP doesn't make sense, because we won't port to CUDA. So it's the choice between HCC (using rocFFT) and C+OpenCL (using clFFT). What would be your choices for an embedded system regarding long time support (~10 years)? |
Hi,
are there plans for OpenCL 2.0 / Shared Virtual Memory support in the near future?
Especially the use of coarse grained svm would be very handy on AMD APUs.
The text was updated successfully, but these errors were encountered: