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
I am pretty certain that the Cray FTN compiler is fortran 2018 compliant. Yet our configury is claimin its missing numerous features.
I think its more likely we have bad fortran code in our configury tests.
Here's the output of the cray fortran compiler for our test that checks for storage size:
(ompi-docs-venv) hpp@ro-rfe4[]:~>crayftn -c storage_size.f90
size = storage_size(x) / 8
^
ftn-412 ftn: ERROR STORAGE_SIZE_COMPLEX32_R1, File = storage_size.f90, Line = 32, Column = 25
This whole array reference of an assumed-size array is not allowed.
size = storage_size(x) / 8
^
ftn-412 ftn: ERROR STORAGE_SIZE_INT32_R1, File = storage_size.f90, Line = 48, Column = 25
This whole array reference of an assumed-size array is not allowed.
size = storage_size(x) / 8
^
ftn-412 ftn: ERROR STORAGE_SIZE_REAL32_R1, File = storage_size.f90, Line = 64, Column = 25
This whole array reference of an assumed-size array is not allowed.
Looks like an audit is needed of all of our fortran test cases, particularly those testing for Fortran 2008 and later features.
The text was updated successfully, but these errors were encountered:
I am pretty certain that the Cray FTN compiler is fortran 2018 compliant. Yet our configury is claimin its missing numerous features.
I think its more likely we have bad fortran code in our configury tests.
Here's the output of the cray fortran compiler for our test that checks for storage size:
Looks like an audit is needed of all of our fortran test cases, particularly those testing for Fortran 2008 and later features.
The text was updated successfully, but these errors were encountered: