Profiling data missing in aocl report for OpenCL kernel

[okramer]

I'm working with an Arria 10GX dev board. I'm trying to view profiling info using "aocl report" but the report doesn't give much info. Here's my kernel compilation command along with dumps:

$ aoc -v -board=a10gx_hostpipe -profile src/SimpleKernel.cl$ cat profile.mon 0,2,SimpleKernel,245929434414546,0,20,8192,1770,8,128,0,8192,1770,8,128,0,6144,1761,6,96,0,1855,0,0,0,0 0,2,SimpleKernel,245929434414546,245929434661675,20,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0$ aocl report SimpleKernel.aocx profile.mon SimpleKernel.source WARNING: Selected File does not have the same path as the file's path stored in .aocx file! May result in blank data. Selected file is /home/okramer/simpleopencl/device/SimpleKernel.cl Path stored in .aocx is device/SimpleKernel.cl

The "aocl report" warning is worrisome, but I don't know what to do about it. I don't see where it's getting the "Selected file" for the kernel source (even though it is correct -- my kernel source is in a different directory than the output -- AH! Maybe that's my problem???)

Is this expected behavior? How do I get values under the "Source Code" tab?

[MEIYAN_L_Intel · Accepted solution]

Hi,

I found that this is known issues in OpenCL SDK v19.3 and will be fixed in future.

Could you try the workaround as steps below:

1. Run "aocl binedit <aocx file> print .acl.profiler.xml > temp.txt"

2. Open the temp.txt file (preferably in some program that can run find-and-replace)

3. Run "aocl binedit <source file> print .acl.file.0" in order to get the full path of the file (note that if there are multiple source files this should be run with "acl.file.1" and so on)

4. In temp.txt, find all the "filename" and :"file" sections, and replace those paths with the full paths found in the .source file

5. Once all the filenames are changed in the temp.txt file, run "aocl binedit <aocx file> set .acl.profiler.xml temp.txt"

Now the .aocx file should have the same full paths as the .source file, and the gui should open the source view.

Thanks

[okramer]

This worked. Thanks.

Is this fixed in 19.4?

[MEIYAN_L_Intel]

Hi,

This is not fixed in OpenCL SDK v19.4 as it is a new known issue.

Thanks