-fallow-argument-mismatch problem of basic packages (
quadpack) that pre-support
fpm, should it be a problem?
- fortran-fans/fftpack at fftpack5.1 forked from certik/fftpack (github.com)
- brocolis/QuadPack (github.com)
- NCAR/ncl/issue#123: Build failure with gfortran 10 (github.com)
- GCC 10 Release Series Changes, New Features, and Fixes
Mismatches between actual and dummy argument lists in a single file are now rejected with an error. Use the new option
-fallow-argument-mismatchto turn these errors into warnings; this option is implied with
-Wargument-mismatchhas been removed.
gcc10 changes routine argument mismatches from warnings to errors by default, this affects
quadpack packages, so we need to tell
gcc10 users to add flag:
-fallow-argument-mismatch when adding
fpm support to
gcc will report an error.
Perhaps for us, it is relatively simple to add easy-to-use interfaces for
quadpack. Modifying the source code to eliminate the problem of argument mismatch requires high professional knowledge.
Should we treat this issue as a problem?
- Managing flags · Issue #112 · fortran-lang/fpm (github.com)
- Draft - Compiler flags profiles by kubajj · Pull Request #498 · fortran-lang/fpm (github.com)
- fpm/fpm.toml at Draft - Compiler flags profiles by kubajj · Pull Request #498 · fortran-lang/fpm (github.com)
So far, we must rely on
-fallow-argument-mismatch to use such
fpm packages, and all need to be manually input
--flag to the command line. This is not user friendly.
Can actions like
fpm help these libraries solve this problem? For example, add such
--flag option to
netlib/dfftpack1.0 (fftpack4.0) is different from
fftpack5.1. The former does not have the problem of
argument-mismatch, while the latter is an updated version with bugs revised and multi-dimensional fft support added.