Is the buil-in profiler still alive in Cuda 3.2? I don’t find any info, and I’m not getting results in 3.2 using the same steps I’ve been using in previous releases (set env variables, and set a config file under ./.config)
–
JL
Is the buil-in profiler still alive in Cuda 3.2? I don’t find any info, and I’m not getting results in 3.2 using the same steps I’ve been using in previous releases (set env variables, and set a config file under ./.config)
–
JL
The built-in profiler (command line profiler) should work as with previous versions of CUDA. Is the profiler output file empty? Or it contains only the header rows with no profiler data rows? Is your application cleaning up all resources and exiting properly? Please provide more details.