I have a 290X and vega64 in the same system, the v64 is the primary card, however in the context of openCL it's device '1', with the 290X being '0'. This is all running windows 10 pro 64 with the latest 18.3.4 drivers.
With the APP SDK 3.0 examples, many will fail to compile or operate on the vega64, but will operate perfectly fine on the 290X (which is the default device, despite being the second card).
A couple I've found so far;
- GlobalMemoryBandwidth returns " clEnqueueSVMMap (inputSVMBuffer) failed! Error code : CL_OUT_OF_RESOURCES "
- FFT returns 31 compile errors, top one being " unknown type name 'class' ", rather obvious that CL 2+ isn't working there...
I haven't tested absolutely all of them, but most of them seem to work just fine, are these issues already known with vega? I haven't been able to find anything about it...
edit; ok so after removing the 290X, GlobalMemoryBandwidth now works correctly, so that could be either a bug with it itself and multiple cards, or a particular driver bug with multiple cards. FFT still returns the same compile errors however...
Hi Paul,
Thank you for reporting this issue. APP SDK 3.0 is quite old, so I don't think APP SDK was tested with the newer cards like vega. Also, it might be a driver issue too. Anyway, I'll report the problem to the concerned team. Please share the clinfo output.
Btw, may I assume that you observed this errors with the pre-built sample binaries available in APP SDK?
To understand the issue better, it would be helpful if you try some older drivers and let us know your observation.
FFT kernel contains static c++ code, hence compilation flag "-x clc++" is used to build the kernel. From the above error, it looks like the compiler failed to recognize the static c++ code.
P.S. You have been whitelisted now.