Hi All,
I have difficulty using V20.9 to compile ioapi-3.2 [https://github.com/cjcoats/ioapi-3.2](https://github.com/cjcoats/ioapi-3.2) nvfortran would stop on compiling interp3.F [https://github.com/cjcoats/ioapi-3.2/blob/master/ioapi/interp3.F](https://github.com/cjcoats/ioapi-3.2/blob/master/ioapi/interp3.F) with fort2 terminated by signal 11.
I was able to compile the package with legacy pgfortran 18.10 and 19.10 without issue.
Thanks in advance for any suggestion on how to proceed.
Winston
detail follows:
cd /r/whao/air3/ioapi-3.2/Linux2_x86_64pg; nvfortran -c -DF90=1 -DFLDMN=1 -DAUTO_ARRAYS=1 -DF90=1 -DNDEBUG -O2 -V -Mnosecond_underscore -DFLDMN=1 -DAUTO_ARRAYS=1 -DF90=1 -DNDEBUG -I/r/whao/air3/ioapi-3.2/ioapi /r/whao/air3/ioapi-3.2/ioapi/interp3.F
NVFORTRAN/x86-64 Linux 20.9-0
Copyright (c) 2019, NVIDIA CORPORATION. All rights reserved.
NVFORTRAN/x86-64 Linux 20.9-0
Copyright (c) 2019, NVIDIA CORPORATION. All rights reserved.
nvfortran-Fatal-/space1/nvidia/hpc_sdk/Linux_x86_64/20.9/compilers/bin/tools/fort2 TERMINATED by signal 11
Arguments to /space1/nvidia/hpc_sdk/Linux_x86_64/20.9/compilers/bin/tools/fort2
/space1/nvidia/hpc_sdk/Linux_x86_64/20.9/compilers/bin/tools/fort2 /tmp/nvfortrance-gkzgYoK3.ilm -fn /r/whao/air3/ioapi-3.2/ioapi/interp3.F -opt 2 -version -terse 1 -inform warn -x 51 0x20 -x 119 0xa10000 -x 122 0x40 -x 123 0x1000 -x 127 4 -x 127 17 -x 19 0x400000 -x 28 0x40000 -x 120 0x10000000 -x 70 0x8000 -x 122 1 -x 125 0x20000 -quad -vect 56 -y 34 16 -x 34 0x8 -x 32 36700160 -y 19 8 -y 35 0 -x 42 0x30 -x 39 0x40 -x 39 0x80 -x 59 4 -x 129 2 -tp haswell -x 120 0x1000 -x 124 0x1400 -y 15 2 -x 57 0x3b0000 -x 58 0x48000000 -x 49 0x100 -astype 0 -x 121 1 -x 183 4 -x 121 0x800 -x 68 0x1 -x 8 0x40000000 -x 70 0x40000000 -x 56 0x10 -x 54 0x10 -x 249 90 -x 68 0x20 -x 70 0x40000000 -x 8 0x40000000 -x 164 0x800000 -x 85 0x2000 -x 85 0x4000 -x 68 0x1 -x 39 4 -x 56 0x10 -x 124 1 -y 163 0xc0000000 -x 189 0x10 -y 189 0x4000000 -x 9 1 -x 72 0x1 -x 136 0x11 -x 37 0x481000 -y 119 0x2000000 -cmdline ‘+nvfortran /r/whao/air3/ioapi-3.2/ioapi/interp3.F -V -c -DF90=1 -DFLDMN=1 -DAUTO_ARRAYS=1 -DF90=1 -DNDEBUG -O2 -Mvect=simd -Mnosecond_underscore -DFLDMN=1 -DAUTO_ARRAYS=1 -DF90=1 -DNDEBUG -I/r/whao/air3/ioapi-3.2/ioapi’ -stbfile /tmp/nvfortranse-2AIcgai2.stb -asm /tmp/nvfortranse-25HUNXkQ.ll
nvfortran 20.9-0 LLVM 64-bit target on x86-64 Linux -tp haswell
NVIDIA Compilers and Tools
Copyright (c) 2020, NVIDIA CORPORATION. All rights reserved.
Makefile:284: recipe for target ‘interp3.o’ failed
make: *** [interp3.o] Error 127
Thanks Winston. I was able to recreate the error here and have added a problem report (TPR#29136). We’ll have a compiler engineer investigate it. Looks like the error first started with the 20.1 release.
-Mat
Hi All,
I have the same problem with this topic, that Nvfortran would stop on compiling interp3.F with fort2 terminated by signal 11.
However, I downloaded and installed the community edition of the PGI Compiler 19.10 in Oct. 2019. My license has expired.
I would like to know how I can download the older version of PGI Compiler.I just want to compile ioapi-3.2 as soon as possible.
Thank you very much.
Mat,
I can also confirm this error on an install of HPC-SDK 20.9.
- Is TPR#29136 publicly viewable (url)?
- Is this issue fixed in HPC-SDK 20.11?
- Is this issue fixed in HPC-SDK 21.1?
I see this thread is still open. I get a similar error when I compile an old program. The program was written >10 years ago and it worked without error using older versions of PG fortran.
Any updates on TPR#29136?
I would really appreciate your suggestions.
Archana
$nvfortran 2D_1Dsolute_diff_FIN_SUBR.cuf -acc -mp=gpu -Minfo=mp solute_diff
2D_1Dsolute_diff_FIN_SUBR.cuf:
nvfortran-Fatal-/opt/nvidia/hpc_sdk/Linux_x86_64/23.11/compilers/bin/tools/fort2 TERMINATED by signal 11
Arguments to /opt/nvidia/hpc_sdk/Linux_x86_64/23.11/compilers/bin/tools/fort2
/opt/nvidia/hpc_sdk/Linux_x86_64/23.11/compilers/bin/tools/fort2 /tmp/nvfortranL69XV8A64R6-.ilm -fn 2D_1Dsolute_diff_FIN_SUBR.cuf -opt 2 -terse 1 -inform warn -x 51 0x20 -x 119 0xa10000 -x 122 0x40 -x 123 0x1000 -x 127 4 -x 127 17 -x 19 0x400000 -x 28 0x40000 -x 120 0x10000000 -x 70 0x8000 -x 122 1 -x 125 0x20000 -quad -x 59 4 -tp tigerlake -x 120 0x1000 -x 124 0x1400 -y 15 2 -x 57 0x3b0000 -x 58 0x48000000 -x 49 0x100 -astype 0 -x 121 1 -x 137 1 -x 121 0xc00 -x 180 0x4000000 -cudaver 12030 -x 183 4 -x 121 0x800 -x 68 0x1 -x 8 0x40000000 -x 70 0x40000000 -x 56 0x10 -x 54 0x10 -x 180 0x4000000 -x 194 0x20000000 -x 233 0x1 -x 205 2 -x 233 0x100 -x 233 0x400 -x 249 160 -x 68 0x20 -x 176 0x100 -cudacap 70 -cudacap 75 -cudacap 80 -cudacap 86 -cudacap 89 -cudacap 90 -cudaver 12030 -x 70 0x40000000 -x 8 0x40000000 -x 164 0x800000 -x 71 0x2000 -x 71 0x4000 -x 34 0x40000000 -x 120 0x1000000 -x 73 0x04 -x 68 0x1 -x 39 4 -x 56 0x10 -x 26 0x10 -x 26 1 -x 56 0x4000 -x 124 1 -accel tesla -accel tesla -x 197 0 -x 175 0 -x 203 0 -x 204 0 -x 180 0x4000400 -x 121 0xc00 -x 186 0x80 -x 180 0x4000400 -x 121 0xc00 -x 194 0x40000 -x 163 0x1 -x 186 0x80000 -cudaver 12030 -x 176 0x100 -cudacap 70 -cudacap 75 -cudacap 80 -cudacap 86 -cudacap 89 -cudacap 90 -cudaroot /opt/nvidia/hpc_sdk/Linux_x86_64/23.11/cuda/12.3 -x 180 0x4000400 -x 121 0xc00 -x 186 0x80 -x 163 0x1 -x 186 0x80000 -cudaver 12030 -x 194 0x40000 -x 176 0x100 -cudacap 70 -cudacap 75 -cudacap 80 -cudacap 86 -cudacap 89 -cudacap 90 -x 189 0x8000 -y 163 0xc0000000 -x 189 0x10 -y 189 0x4000000 -cudaroot /opt/nvidia/hpc_sdk/Linux_x86_64/23.11/cuda/12.3 -x 187 0x40000 -x 187 0x8000000 -x 60 512 -mp -x 69 0x200 -x 69 0x400 -x 69 2 -x 0 0x1000000 -x 2 0x100000 -x 0 0x2000000 -x 161 128 -x 162 128 -cci /tmp/nvfortrann69XNIsuf6DI.cci -cmdline ‘+nvfortran 2D_1Dsolute_diff_FIN_SUBR.cuf -acc -mp=gpu -Minfo=mp’ -stbfile /tmp/nvfortran169XF3gXH7_p.stb -asm /tmp/nvfortranv69X-a_6rOxe.ll
TPR#29136 appears to have been resolved a few years ago - if you want to open a new problem about the issue that what you’re seeing, could you please open a new thread, try to provide a minimally reproducing example that we can take and experiment with, and carefully outline the exact error that you’re seeing? That would make helping resolve or report your issue to engineering much easier! Thank you in advance!