AnsweredAssumed Answered

Bad columns in OpenCL profiling in CodeXL 2.0

Question asked by et@et3d on Apr 21, 2016
Latest reply on May 10, 2016 by et@et3d

I'm profiling using the VS2013 plugin on a Fury X with drivers 16.4.1.

 

The Time column shows 0 for everything. The LocalMemSize column shows numbers like 00592, 03616, etc., which I assume (based on my familiarity with the program's performance) are execution times (0.0592 ms, 0.3616 ms), the VGPRs column shows 0, and many other columns are 0.

Outcomes