Hi Juan,
Apologies. I missed the other questions.
What library isn’t being found? libcupti.so? If so, then that’s the device side profiler so you may need to include the directory where it’s found in your LD_LIBRARY_PATH environment variable. With 20.7, it can be found in “/Linux_x86_64/20.7/profilers/Nsight_Systems/target-linux-x64/”
Though, Nsight-Systems does trace OpenACC by default so you need to include the “openacc” option in the trace flag (–trace, or -t) for the “profile” command.
% nsys --help profile
....
-t, --trace=
Possible values are 'cuda', 'nvtx', 'osrt', 'cublas', 'cudnn', 'opengl', 'mpi', 'openacc', 'openmp', 'vulkan' or 'none'.
Select the API(s) to trace. Multiple APIs can be selected, separated by commas only (no spaces).
If 'none' is selected, no APIs are traced.
Default is 'cuda,opengl,nvtx,osrt'. Application scope.
nvfortran , warn about compiling for -acc=multicore,gpu , but code is working fine apparently ( and this was OK with PGI version ) :
It’s just a warning and works the same as before. We’ve actually never fully supported combining the two. It works in most cases, but we know of a few problems that we’ve not been able to resolve. They do work together for most codes, but the message is just asserting that we may not be able to fix an issue when it doesn’t work (i.e. supported).
Engineering decided to make this more explicit by adding the warning. Though, you’re right that the text of the message makes it seem like they can’t be used together, and we’re thinking ways to change the message to make this more clear. Apologies that the message is confusing.
-Mat