Thanks for the report! I added TPR#26338 to track this issue.
Luckily there are several work arounds.
First, the issue does not occur in our LLVM back-end compilers, so you can add “-Mllvm” to you compiler flags, or point your PATH to use the llvm compilers instead of the default native x86 compilers.
Alternatively you can add “-Mframe” and/or “–no_exceptions” to the compilation. The error appears that when “-Mnoframe” is applied, we’re missing one of the exception handler frames. Hence using “-Mframe” will keep the frame pointers, or “–no_exceptions” will remove exception handling.
I have a new problem with this lab. When I profile the initial sequential code of OpenACC lab2 using pgprof 18.1 or nvprof 9.0.176, following the same instrucctions of the lab:
nvprof --cpu-profiling on --cpu-profiling-mode top-down ./cg
I get the following output:
======== CPU profiling result (top down):
Time(%) Time Name
99.67% 21.1572s ???
99.67% 21.1572s | main
0.14% 30.225ms | munmap
0.19% 40.299ms __c_mcopy8
0.14% 30.225ms __c_mset8
where the most time-consuming functions are not even recognized…