PGI User Forum

donb · Posted: Fri Jul 16, 2010 10:24 am Post subject:

Mark,
Thanks for the feedback.

On the config file location, I will make sure that is fixed in the next release. If you want to be notified directly of changes in status on this issue, email trs@pgroup.com and ask to be added to the notification list for TPR #17102.

Regarding profiling of PGI Accelerator Model (!$acc) vs. CUDA Fortran:

We currently use two different methods of performance data collection for these two programming models. The 'pgcollect -cuda' option should only be used for CUDA Fortran. Just use 'pgcollect -time' for the Accelerator Model approach.

With -cuda and CUDA Fortran, you can get GPU counter information.

With the Accelerator Model and pgcollect, you get information similar to what you get when you compile with '-ta=time', but with more correlation to source code and compiler feedback.

In time we will merge these two methods.

--Don

Mark Abene · Joined: 05 Oct 2009 Posts: 4

We got it. Makes sense now.

Thanks,
-Mark

donb · Posted: Wed Jul 21, 2010 1:36 pm Post subject:

Just an update: the issue of looking in the wrong location for CUDA fortran profiling config files only shows up when you use the -cuda option with no keywords.

If you use '-cuda=gmem', '-cuda=branch', or '-cuda=cfg:_config_file_', you shouldn't see this problem. You can create your own config file listing which ever counters you want to use, within the limitations of the counter support on your particular GPU.

--Don