Draft
Conversation
rtodling
approved these changes
Sep 22, 2023
Collaborator
rtodling
left a comment
There was a problem hiding this comment.
These are fine by me. Branch might need update though.
Member
Author
Yeah. I need to revisit this. Files got moved long ago... I'll put it on the list! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR tracks changes needed to compile GMAO_Shared with the NAG Compiler. NAG is very strict and will not allow the use of Fortran extensions that are endemic to GEOS.
The first category are procedures that are now part of the Fortran Standard that used to be extensions in some compilers:
iargc()→command_argument_count()getarg()→get_command_argument()getenv()→get_environment_variable()system()→execute_command_line()call exit(0)→stopcall exit(N)→error stop NNAG also doesn't support (without flags that need to be used everywhere as @tclune can elucidate on) the use of
real*4orreal(kind=4). The reason is that NAG does not use 4 for 32-bit real and 8 for 64-bit, instead they use 1 and 2. (The Standard does not specify what "kind" a 32-bit real must be, only that there must be one.) So, many changes are of the type:real*4→real(REAL32)real(kind=8)→real(kind=REAL64)