Closed osbama closed 2 years ago
Dear Osbma, thanks for reaching out. Indeed we did something similar in the develop (private) branch
*nvfortran* )
SYSFLAGS="-O2 -g -fast -Munroll -Mnoframe -Mdalign -Mbackslash"
FUFLAGS="-O0 -Mbackslash"
FCMFLAG="-Mnomain"
OMPFLAGS="-mp"
NETCDFFLAGS="-DpgiFortran"
def_compiler="-D_PGI"
DEBUG_FLAGS="-g -Minform=inform -Mbounds -Mchkptr -Mchkstk -Meh_frame -Mbackslash"
and we are working on something more refined on a dedicated branch.
We also fixed acx_get_fc_kind.m4
For release 5.0 I'll let the fix enter in the next patch.
Dear developers,
I am trying to compile YAMBO with NVIDIA HPC SDK 21.3 in order to benefit from GPUs in our cluster. The Fortran compiler bundled there identifies itself as nvfortran, however acts almost identical to PGI compiler.
PGI compiler has some different ideas on how to interpret sources. I see workarounds for them are already implemented, i.e. in
src/modules/mod_stderr.F
with a preprocessor option_PGI
Since
configure
does not recognizenvfortran
as a PGI compiler, these workarounds are ignored.I suggest adding
nvfortran
toconfig/m4/acx_get_fc_kind.m4
as a PGI compiler derivativeEdit: It seems
acx_fortran_flags.m4
acts independently fromacx_get_fc_kind.m4
. nvfortran needs to be added there as well.