module m
use ieee_arithmetic
end module m
submodule(m) s
!use ieee_arithmetic
end submodule s
$ nvfortran --version
nvfortran 20.11-0 LLVM 64-bit target on x86-64 Linux -tp haswell
NVIDIA Compilers and Tools
Copyright (c) 2020, NVIDIA CORPORATION. All rights reserved.
$ nvfortran -c bug.f90
nvfortran-Fatal-/opt/nvidia/hpc_sdk/Linux_x86_64/20.11/compilers/bin/tools/fort1 TERMINATED by signal 11
Arguments to /opt/nvidia/hpc_sdk/Linux_x86_64/20.11/compilers/bin/tools/fort1
/opt/nvidia/hpc_sdk/Linux_x86_64/20.11/compilers/bin/tools/fort1 bug.f90 -opt
1 -terse 1 -inform warn -nostatic -x 19 0x400000 -quad -x 59 4 -x 15 2 -x 49
0x400004 -x 51 0x20 -x 57 0x4c -x 58 0x10000 -x 124 0x1000 -tp haswell -x 57
0xfb0000 -x 58 0x78031040 -x 47 0x08 -x 48 4608 -x 49 0x100 -stdinc
/opt/nvidia/hpc_sdk/Linux_x86_64/20.11/compilers/include-
gcc70:/opt/nvidia/hpc_sdk/Linux_x86_64/20.11/compilers/include:/usr/lib/gcc/x86_
64-linux-gnu/9/include:/usr/local/include:/usr/include/x86_64-linux-
gnu:/usr/include -cmdline '+nvfortran bug.f90 -c' -def unix -def __unix -def
__unix__ -def linux -def __linux -def __linux__ -def __NO_MATH_INLINES -def
__LP64__ -def __x86_64 -def __x86_64__ -def
__LONG_MAX__=9223372036854775807L -def '__SIZE_TYPE__=unsigned long int' -
def '__PTRDIFF_TYPE__=long int' -def __amd64 -def __amd64__ -def __k8 -def
__k8__ -def __MMX__ -def __SSE__ -def __SSE2__ -def __SSE3__ -def __SSSE3__
-def __SSE4_1__ -def __SSE4_2__ -def __AVX__ -def __AVX2__ -def __FMA__ -def
__XSAVE__ -def __POPCNT__ -def __FXSR__ -def __PGLLVM__ -def
__NVCOMPILER_LLVM__ -def __extension__= -freeform -vect 48 -x 54 1 -x 68 0x1 -
x 70 0x40000000 -x 70 0x40000000 -x 68 0x1 -x 124 1 -x 195 0x8000 -y 163
0xc0000000 -x 189 0x10 -stbfile /tmp/nvfortrannGuNiJaePSi.stb -modexport
/tmp/nvfortran1GuFnC-ehXv.cmod -modindex /tmp/nvfortranDGux5Djxd8X.cmdx -
cci /tmp/nvfortranLGuVYCgWOZ8.cci -output /tmp/nvfortran9Gu3tQEDlBA.ilm
Thanks mehdi.chinoune!
I was able to reproduce the issue here and have sent a problem report (TPR #29474) to our compiler engineers for further investigation.
-Mat
This has been fixed in our 21.3 release. Thanks for the bug report.