NCAR / NCAR/ccpp-framework

Fortran #5462: Global name too long

Open
#786 8 comments 0 reactions 1 assignee View on GitHub

@climbfuji is already working on this.

Since Sep 16, 2026.

bug
Dominant language
Python
Stars
25
Forks
67
Avg merge
3d 8h
Merged PRs (30d)
2

Description

Description

In WM PR 3174, RT logs showed no warnings or remarks for most compiles. However, when we turned on WARN_AS_ERROR in the PR, it produced several "global name too long" warnings, mostly from CCPP. For example:

/scratch4/NAGAPE/epic/Gillian.Petro/stmp/RT_RUNDIRS/Gillian.Petro/FV3_RT/rt_4056323/compile_s2swa_32bit_oneapi/build_fv3_s2swa_32bit_oneapi/UFSATM/ccpp/ccpp/ccpp_FV3_GFS_v17_coupled_p8_ugwpv1_cap.F90(233): error #5462: Global name too long, shortened from: ccpp_fv3_gfs_v17_coupled_p8_ugwpv1_cap_mp_FV3_GFS_V17_COUPLED_P8_UGWPV1_PHYSICS_TIMESTEP_INIT to: p_fv3_gfs_v17_coupled_p8_ugwpv1_cap_mp_FV3_GFS_V17_COUPLED_P8_UGWPV1_PHYSICS_TIMESTEP_INIT
  subroutine FV3_GFS_v17_coupled_p8_ugwpv1_physics_timestep_init( &
-------------^
/scratch4/NAGAPE/epic/Gillian.Petro/stmp/RT_RUNDIRS/Gillian.Petro/FV3_RT/rt_4056323/compile_s2swa_32bit_oneapi/build_fv3_s2swa_32bit_oneapi/UFSATM/ccpp/ccpp/ccpp_FV3_GFS_v17_coupled_p8_ugwpv1_cap.F90(527): error #5462: Global name too long, shortened from: ccpp_fv3_gfs_v17_coupled_p8_ugwpv1_cap_mp_FV3_GFS_V17_COUPLED_P8_UGWPV1_PHYSICS_TIMESTEP_FINAL to: _fv3_gfs_v17_coupled_p8_ugwpv1_cap_mp_FV3_GFS_V17_COUPLED_P8_UGWPV1_PHYSICS_TIMESTEP_FINAL
  subroutine FV3_GFS_v17_coupled_p8_ugwpv1_physics_timestep_final( &
-------------^

It seems unnecessary for the names to be so long, since there is duplicate info. For example, "ccpp_fv3_gfs_v17_coupled_p8_ugwpv1" is repeated twice in the name. Even though error 5462 is disabled in ufs-weather-model/cmake/IntelLLVM.cmake, when WARN_AS_ERROR is on, the out file shows Cannot disable Fortran error message 5462 and compilation fails.

Steps to Reproduce

Provide the tag or hash of the CCPP Framework used to reproduce the bug: c4b7d9a (I think this corresponds to tag capgen-1.0.0-pre.

Have you make any modifications to the CCPP Framework code? No.

  1. Clone WM PR 3174: git clone --recursive -b feature/ss2.x https://github.com/gspetro-NOAA/ufs-weather-model.git 3174
  2. Run any of these compiles from the ufs-weather-model/tests directory:
    • s2swa_32bit_oneapi
    • s2sw_32bit_pdlib_oneapi
    • s2sw_oneapi
    • s2swl_oneapi
    • s2s_aoflux_oneapi
    • s2sw_pdlib_oneapi
    • csawmg_oneapi
    • wam_oneapi
    • hafsw_oneapi
    • hafs_mom6w_oneapi
    • hafs_all_oneapi
    • atm_ds2s_docn_pcice_oneapi
    • atmw_oneapi
    • atmaero_oneapi
    • atmaq_oneapi
  3. View the err and out files to see the details of the errors/warnings/remarks.

Additional Context

Please provide any relevant information about your setup. This is important in case the issue is not reproducible except for under certain conditions.

  • Machines: Ursa, Hercules, Orion, and Gaea C6
  • Compiler: OneAPI (LLVM)
  • Suite Definition File or Scheme: Set via COMPILE line in rt.conf; differs based on the compile job.
  • Reference other issues or PRs in other repositories that this is related to, and how they are related: There is a whole host of sub-PRs under WM PR 3174, as well as related issues in each repo. See the main PR for the links.

Output

Please include any relevant log files, screenshots or other output here.

Run directories:

  • Ursa: /scratch4/NAGAPE/epic/Gillian.Petro/stmp/RT_RUNDIRS/Gillian.Petro/FV3_RT/rt_4056323
  • Hercules: /work2/noaa/epic/gpetro/hercules/RTs/ufs-wm/stmp/gpetro/FV3_RT/rt_3294532

Test directories:

  • Ursa: /scratch3/NAGAPE/epic/Gillian.Petro/ursa/RTs/ufs-wm/pretests/3174/tests
  • Hercules: /work2/noaa/epic/gpetro/hercules/RTs/ufs-wm/pretests/3174/tests

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.