On non-AMD systems, timer-based profiling is the only method of profiling supported.
When you launch an OpenCL application from CodeAnalyst for a timer-based profile, the OpenCL information will be available as expected from the overview.
Does that make sense?
Thank you, Frank.
Indeed the computer is running non-AMD central processor. But I don't see any OpenCL information at overview page while the application definately runs kernels at AMD Cayman GPU. All I see are two blocks: "Target application info" and "System-wide Profile".
1) What version of the AMD APP SDK are you using? CodeAnalyst has been extensively tested with the latest version. It's available from http://developer.amd.com/sdks/AMDAPPSDK/downloads/Pages/default.aspx.
2) In the session settings dialog, are you launching the OpenCL application? Is the duration "Until app exit"? Is the CPU Utilization checked?
Please let us know how it works out.
I guess it is APP SDK 2.5something installed with Catalyst 11.7 preview. I successfully profile the application with AMD APP Profiler plugin for VS2010.
> are you launching the OpenCL application?
> Is the duration "Until app exit"?
> Is the CPU Utilization checked?
No. I checked it and now I see Utilization block, but without any OpenCL info there.
P.S. AMD-APP-SDK-v2.5 (684.211)
We want to check that the profiling agent is hooking up correctly on your system. From CodeAnalyst, set the duration to a reasonable amount of time and start the profile. From a command prompt on a 32-bit system, would you please type set CL_AGENT=oclProfAgent32.dll and then execute the OpenCL application. (For a 64-bit system, use set CL_AGENT=oclProfAgent64.dll)
Are you able to get OpenCL results this way?
Please note that CodeAnalyst does not officially support untested versions of the APP SDK.
> Are you able to get OpenCL results this way?
> Please note that CodeAnalyst does not officially support untested versions of the APP SDK.
I understand it. But it is a little strange for AMD to advertise gDEBugger (not alpha, not beta) for which one should install untested version of Catalyst (and APP SDK installed with it).
Well, it is not your fault anyway. Thank for trying! I will continue using AMD APP Profiler.
I was unable to reproduce your issue when I installed the Catalyst 11.7 from the same link.
Is the CodeAnalyst\bin directory in your path? You might try specifying the full path to the profile agent, for example: set CL_AGENT=c:\Program Files\AMD\CodeAnalyst\bin\oclProfAgent32.dll