-
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
Audit the compiler flags used to build on gadi with the Intel compiler #12
Comments
oasis3-mct
|
libaccessom2
|
cice5
|
mom5
|
This issue has been mentioned on ACCESS Hive Community Forum. There might be relevant details there: |
The |
Note that I am not volunteering to do this, but it would be good to extract out the exact flags used in each model and chuck it in a table or similar to be able to compare them across models. |
might be easiest to build access-om2 and copy from what it echoes to the terminal |
Notes
|
Notes |
Notes |
Notes |
|
Hi @penguian & @micaeljtoliveira , your feedback will be appreciated. |
Hi, I'm afraid I don't have much else to add. I would add backtrace by default to all builds, as it has no performance penalty and it can be useful to track down why some calculation failed in production. You can also consider adding any check done by the compiler at compile time. Their only caveat is that they make compilation slower. |
From @aekiss on the ACCESS-Hive forum (https://forum.access-hive.org.au/t/audit-the-compiler-flags-used-to-build-access-om2-on-gadi-with-the-intel-compiler/437): Good question. Many of these were chosen after careful investigation, e.g. work by Paul Leopardi (NCI) on reproducibility between Gadi and the previous system (Raijin), and scaling on Gadi - see
MOM CICE libaccessom2 oasis |
In oasis3-mct, it was added via commit ACCESS-NRI/oasis3-mct@601de2c |
Notes
|
Just spoke with @penguian, these flags were not intended to be enabled by default. |
@aidanheerdegen asked the question, "Is Currently, I default to |
@penguian and I were chatting about
|
Document compiler flags of the following components:
The text was updated successfully, but these errors were encountered: