I have a complex Visual Studio 2015 project, with a lot of C++ host code, and many .cl files.
So far, I have been developing "by instinct", using theoretical understanding of GPU architecture
to optimize and design the code. This approach has worked quite well so far, but it is time consuming.
I am ready to take things to the next level, by looking at low level machine code, occupancy, etc.
Can anyone recommend a good approach for me to start using CodeXL on my project?
Solved! Go to Solution.
Hi,
CodeXL does not yet have a Visual Studio 2015 extension.
You can use the CodeXL standalone application to debug, profile and analyze your application and CL code.
Follow the Quick Start Guide (from the menu Help -> Quick Start Guide), to learn how to use CodeXL debugging, profiling and analysis features.
You can also check out the recorded CodeXL 1.7 webinar which demonstrates many of CodeXL features: Power Profiling, Shader Analysis & More with AMD CodeXL 1.7 - YouTube
Doron
Hi,
CodeXL does not yet have a Visual Studio 2015 extension.
You can use the CodeXL standalone application to debug, profile and analyze your application and CL code.
Follow the Quick Start Guide (from the menu Help -> Quick Start Guide), to learn how to use CodeXL debugging, profiling and analysis features.
You can also check out the recorded CodeXL 1.7 webinar which demonstrates many of CodeXL features: Power Profiling, Shader Analysis & More with AMD CodeXL 1.7 - YouTube
Doron
Thanks, Doron. That is exactly what I was looking for.
Unfortunately, I can't profile my code because my project makes heavy usage of OpenCL user events,
and the profiler doesn't support user events. Are there plans to support this feature in the future?
Got this working. I had queued all of my kernels up in advance, to be triggered by a user event. The profiler didn't like that. When I disabled that one user event, profiling started working.
Indeed, it would be really nice if the Add-In would work. Regard this as a +1 on the feature request list.
Keep up the good work guys. Tooling is essential.
Hi,
Thanks for the feedback.
We consider the CodeXL Visual Studio 2015 extension a high priority feature, and it is prioritized accordingly. I can't disclose details of future releases but that should speak for itself.
Doron
Hello Doron, Any updates by chance on Visual Studio 2015 support for codeXL? Thanks. Ryan