You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and the problem is with trim(attribute_value(1:str_len)) inside of the function call, or something to that effect. (There are few other instances of this sort of operation in FMS).
It appears that removing the (1:str_len) slice fixes the problem. However, this slice operation was included to avoid some issues with PGI Fortran.
I see two ways to resolve this:
Remove the slice operators in FMS2, then point to this updated version. However, this will require careful testing of 2024.01 in our regression suite, which may introduce even more problems. (I know of at least one.)
Disable FMS2 in GitHub Actions, at the cost of not detecting future FMS2 issues.
My opinion: I prefer the first solution, but it will take more time. I am ok with the second solution, as long as we do not stop working on the first.
Currently MOM6 cannot be used with FMS2 IO when compiled with GCC 14.1 We get the following error:
The problem appears to be lines like this in FMS:
and the problem is with
trim(attribute_value(1:str_len))
inside of the function call, or something to that effect. (There are few other instances of this sort of operation in FMS).It appears that removing the
(1:str_len)
slice fixes the problem. However, this slice operation was included to avoid some issues with PGI Fortran.I see two ways to resolve this:
My opinion: I prefer the first solution, but it will take more time. I am ok with the second solution, as long as we do not stop working on the first.
Relevant issues:
This appears in our MacOS testing because its Homebrew packages currently point to GCC 14.1. This is not any unique to MacOS platforms.
There has been a recent GCC update to 14.1.1, but it does appear to resolve this problem.
While not strictly a MOM6 issue, this affects our ability to use FMS2 with the latest GCC.
The text was updated successfully, but these errors were encountered: