The AMD APP SDK 3.0 Beta is available.
Having explored the potential of OpenCL 2.0 via provisional OpenCL 2.0 drivers and our OpenCL 2.0 Demystified blog series, you can now dive deep with AMD’s latest offering: official OpenCL 2.0 drivers and a beta version of the AMD APP SDK 3.0.
That’s great! What does it contain, and why should I care?
AMD APP SDK 3.0 Beta provides samples that illustrate all the major new features of OpenCL 2.0 and a glimpse into the most interesting optional features. These features are already supported on recent APUs and GPUs from AMD (for a full list of supported products, see here), so you can start programming and deploying software with OpenCL 2.0 today. AMD APP SDK 3.0 Beta also supports the Bolt 1.3 library and includes new samples for the Bolt C++ AMP library.
AMD APP SDK 3.0 Beta also provides a new, web-based installer that allows you to download only what you choose, but still distribute the downloaded package locally.
Finally, AMD APP SDK 3.0 Beta includes enhanced documentation. The Getting Started Guide has been restructured to provide quick and relevant information to Windows and Linux users. The FAQ has been updated to include answers to the most pressing questions on OpenCL 2.0. The AMD OpenCL programmer’s guide – the most useful reference manual for OpenCL users – is now repurposed into two documents: the AMD OpenCL user’s guide, containing relevant OpenCL information for basic users; and the AMD OpenCL optimization guide, containing optimization guidelines for advanced users. The AMD OpenCL user’s guide has been revamped with a host of improvements (read about the improvements and provide feedback here), and the AMD OpenCL optimization guide features important updates.
That IS something! I can’t wait to get started.
Neither can we.
All said, it’s still a Beta.
And, be advised...there is one hiccup we're aware of. The Catalyst driver version 14.12 does not support OpenCL 2.0 on FirePro Graphics cards.
To work with OpenCL 2.0:
* On Radeon graphics cards, use the Catalyst Driver linked to above.
* On supported FirePro graphics cards, use the early-release driver available here. That page details the particular cards that are supported.
Your feedback will help us define and improve the quality of our GA offering.
1. Where's the app to precompile kernels into SPIR opcodes pls?
2. No fine-grained SVM support yet?
3. I specify an installation path ( d:/AMDAPPSDK ) but the installer ignored it and copies a lot of things into c:/program files(x86)/AMD APP SDK.
Pending a more detailed answer from Dipak or someone on SPIR...
Marty Johnson's overview of the new APP SDK has a list of the examples included. On that are
* SVM Fine Grain Buffer + Platform Atomics
* SVM Fine Grain Buffer + C11 Atomics - requires Linux APU
I believe there will be a blog article demonstrating fine-grain SVM in the near future, probably January given holidays, but no promises. It's in the works, but sometimes things that are planned don't see the light of day.
I'll get the installer feedback to the team.
Does Catalyst Omega actually have Opencl 2.0 drivers for R9 290X cards...
Mine is reporting 1.2
You can also see this here
|device_version||OpenCL 1.2 AMD-APP (1642.5)|
does it work for Crossfire'ed cards?
I can provide a minor bug report already:
The 64bit linux installer has the following problem: after installation is finished,
1) the icd file is incorrectly added to /etc/OpenCL. It should be /etc/OpenCL/vendors.
2) the environment variable setting file in /etc/profile/ incorrectly sets the opencl vendor directory to INSTALATION_PATH/etc/OpenCL/vendors. It should be just /etc/OpenCL/vendors
For 1), the symptom will be that "clinfo" can't find the AMD CPU driver at all. For 2), after a reboot, "clinfo" will report no usable platforms on the computer, because it's looking in the wrong place.
1) If you are looking for a SIPR generator, you can use any standard SPIR generator like CLANG [KhronosGroup/SPIR · GitHub]. AMD compiler fully supports consumption of SPIR. You may check the SDK sample "SimpleSPIR" to see how to consume SPIR code using OpenCL API.
2) Already answered.
3) When the installation path is changed, it changes the samples installation path. So the samples, which generally go into the %USERPROFILE% directory as of now would go in the d:/AMDAPPSDK directory. The contents of Program Files (x86) are the AMDAPPSDKROOT contents, which as of now cannot be changed via the UI. However if you need to write the AMDAPPSDKROOT contents to a non-standard folder, then the SDK installer can be run from the command line as follows:
1) I would prefer to use a command-line tool from AMD ( like the NVIDIA's nvcc.exe compiler ) or the Intel's IOC tool, honestly !
2) Apparently, OpenCL 2.0 SVM fine grained with atomics full support is currently only available on Kaveri APUs and CPU devices. Not for Radeon 7XXX and neither 2XX GPUs.
We would like to know if they will be full SVM-compatible, thx!
3) Thanks for the turnaround, it worked well. I would rather prefer to install ALL into the dir I specify. I don't like to install SDKs into my C drive(specially into the Program Files dir because it contains spaces and also the x86/x64 problem, some old programs will have problems with that ).
Are you building your app as 32 bit app? It looks like only 64bit OCL library is 2.0. When I built the samples as 32bit executable, I got the same problem.