Bring in NCO Intel DEBUG build changes. #985
Draft
Conversation
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
13 tasks
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.
Description
Bring in NCO DEBUG flag change for ops
NCO requires that all DEBUG builds have at least the following: -check all -ftrapuv
What bug does it fix, or what feature does it add? Meets implementation standards for ops debug builds
Is a change of answers expected from this PR? No
Issue(s) addressed
Testing
How were these changes tested? UFSWM Regression Testing Suite
What compilers / HPCs was it tested with? Gaea C6, Intel
Are the changes covered by regression tests? Yes
Have the ufs-weather-model regression test been run? Yes
On what platform? GaeaC6
Will the code updates change regression test baseline? No
Dependencies