-
Notifications
You must be signed in to change notification settings - Fork 0
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
Decide on FMS compile flags #1
Comments
Example of compilation flags from MOM5 with git subtree FMS ( |
Looks like |
Agreed - I think we want to consistent with what was being done before |
Hi @manodeep , What compiler flags should we use for cmake/compiler_flags_IntelLLVM_C.cmake:
cmake/compiler_flags_IntelLLVM_Fortran.cmake:
|
@harshula Those flags look fine to me. Do you know why the oneAPI compiler returns a fatal error? |
Hi @manodeep Have a look at https://github.com/ACCESS-NRI/FMS/blob/development/CMakeLists.txt and see what happens when I should be able to get back to FMS this week and add Can you please help me by checking each of the compiler flags in #1 (comment) and tell me if any are incompatible with IFX? If they are, please suggest an alternative. |
@harshula Uhh
Fantastic! If it would be helpful, I am happy to jump on a zoom call and try to compile those oneAPI packages out together.
Those flags are compatible with I would really like to add |
Confirming that |
Hi @manodeep , git tag Can you please document all your findings, including what you have documented in this issue, in https://github.com/ACCESS-NRI/dev-docs/wiki/ ? |
Git tag
|
The existing CMakeLists.txt contains the following compile flags:
FMS/CMakeLists.txt
Lines 40 to 64 in 38c7dbe
The upstream FMS compile flags are: 02bdd2f
The MOM5 compile flags are: https://github.com/ACCESS-NRI/MOM5/blob/6d8768648ffa2326b4817c3de9ccb25e9d808585/bin/mkmf.template.nci#L39-L51
Which of them should we use?
The text was updated successfully, but these errors were encountered: