Resolve the HAFS v1.0 compile warnings

[BinLiu-NOAA]

Description

Provide a clear and concise description of the requested feature/capability. From NCO SPA: There are numerous compilation warnings in the HAFS v1.0 builds, shown as below for some samples. Please ensure that these can be compiled cleanly in the next upgrade.

All compilation warning are listed in /lfs/h1/ops/para/packages/hafs.v1.0.3/sorc/logs/warning.list file and here the statists from each sorc builds -

build_forecast.log 363 build_gsi.log 17 build_hycom_utils.log 9 build_post.log 2 build_tools.log 1 build_tracker.log 3 build_utils.log 4 build_ww3_utils.log 0 total 399

Proposed solution

How should the new feature/capability be added? If you have thoughts on the implementation strategy, please share them here.

Status (optional)

Do you (or a colleague) plan to work on adding this feature?

Related to (optional)

Directly reference any related issues or PRs in this or other repositories, and describe how they are related. Examples:

• fixed by hafs-community/hafs/pull/
• dependent upon ufs-community/ufs-weather-model/pull/
• associated with noaa-emc/upp/pull/
• related to hafs-community/GSI/issues/

[BijuThomas-NOAA]

build_forecast.log (741)

• A dummy argument with an explicit INTENT(OUT) declaration is not given an explicit value
• Global name too long, shortened from:(ccpp)

build_post.log(3)

• Some OpenMP processing was skipped to constrain compile time. Consider overriding limits (-qoverride-limits)

build_tracker.log(1)

• gettrk_main.f.o: requires executable stack (because the .note.GNU-stack section is executable)

build_utils.log(4)

• function "insertIntersect" declared implicitly

build_tools.log(1)

• fson_path_m.f90.o: requires executable stack (because the .note.GNU-stack section is executable

build_gsi.log(17)

• CMake Warning at regression/CMakeLists.txt
• A dummy argument with an explicit INTENT(OUT) declaration is not given an explicit value

build_hycom_utils.log(0)

build_ww3_utils.log(0)

[BinLiu-NOAA]

With the great collaborative work and support from the ufs-weather-model and its subcomponents developers, together with the EMC hurricane, wave, post, and data assimilation groups' effort, the build warnings have been significantly reduced (almost eliminated) for the latest HAFSv2 package. The total number of build warnings is reduced from 399 (HAFSv1) to 34 (HAFSv2). Besides, most of the remaining build warning are related to this item of "libjasper.so, may conflict with libjpeg.so.9", which cannot be addressed from the HAFS developers' end.

Here are the left over build warning items for the entire HAFSv2 package:

• build_forecast.log: 4
  • 2 on libjasper.so, may conflict with libjpeg.so.9
  • 2 on /tmp/ifort3Jumqm.i90: warning #6178: The return value of this FUNCTION has not been defined. [MY_POINTER]
• build_gsi.log: 0
• build_hycom_utils.log: 1
  • on libjasper.so, may conflict with libjpeg.so.9
• build_post.log: 1
  • on libjasper.so, may conflict with libjpeg.so.9
• build_tools.log: 0
• build_tracker.log: 4
  • on libjasper.so, may conflict with libjpeg.so.9
• build_utils.log: 3
  • on libjasper.so, may conflict with libjpeg.so.9
• build_ww3_utils.log 21
  • on libjasper.so, may conflict with libjpeg.so.9
• total: 34

[BinLiu-NOAA]

Related issue and PRs to address the ufs-weather-model build warnings can be seen from ufs-community/ufs-weather-model/issues/1984 and ufs-community/ufs-weather-model/pull/2218.