-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix type mismatch compiler error when gfortran 10 is used without '-fallow-argument-mismatch' flag #770
Conversation
Switch from 'use mpi' to 'use mpi_f08'
If output grid is 'cubed_sphere_grid' AND inline post is turned on print error and terminate the model.
Hi, @DusanJovic-NOAA . Are you able to sync up this PR? Following that I can request reviews. |
Done. |
@DusanJovic-NOAA ccpp-physics and framework sub-PRs have been merged. Hashes: |
@DusanJovic-NOAA can you check git action failures?
|
@DusanJovic-NOAA @climbfuji I am not sure if this is gcc or mpich version issue ? |
The mpi_f08 module is missing. Either mpich is compiled without f08 support or there's some issue with the installation. Also on two HPC platforms where we test the gnu compiler we use openmpi, mpich had some issues. I think this should be updated to use openmpi. @AlexanderRichert-NOAA added this CI action. |
I think this line: fv3atm/.github/workflows/GCC.yml Line 44 in 6942270
should end with |
Description
(Instructions: this, and all subsequent sections of text should be removed and filled in as appropriate.)
Starting with version 10 of GNU Fortran compiler, subroutine argument mismatches are flagged as errors, and must be silenced by using '-fallow-argument-mismatch' flag, which can potentially hide actual bugs, which is undesirable.
This PR fixes all such mismatches, mostly by switching to use mpi_f08 MPI module, which provides generic interfaces or by passing correct type of arguments to w3lib calls.
What bug does it fix, or what feature does it add? Avoids the need to silence argument mismatch
Is a change of answers expected from this PR? No
Issue(s) addressed
Link the issues to be closed with this PR, whether in this repository, or in another repository.
(Remember, issues should always be created before starting work on a PR branch!)
Testing
How were these changes tested? ufs-weather-model regression test
What compilers / HPCs was it tested with? GNU and Intel
Are the changes covered by regression tests? Yes
Have the ufs-weather-model regression test been run? Yes. On what platform? Hera
Dependencies
If testing this branch requires non-default branches in other repositories, list them.
Those branches should have matching names (ideally)
Do PRs in upstream repositories need to be merged first?
If so add the "waiting for other repos" label and list the upstream PRs