Are all these compiler flags needed for Debug build?

[edwardhartnett]

In our CMakeFiles.txt we have this for GNU compilers:

set(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -g -fbacktrace")
if(${CMAKE_Fortran_COMPILER_VERSION} VERSION_GREATER_EQUAL 10)
  set(CMAKE_Fortran_FLAGS "${CMAKE_Fortran_FLAGS} -fallow-argument-mismatch -fallow-invalid-boz")
endif()
set(CMAKE_Fortran_FLAGS_DEBUG "-O1 -ggdb -fno-unsafe-math-optimizations -frounding-math -fsignaling-nans -ffpe-trap=invalid,zero,overflow -fbounds-check -fno-omit-frame-pointer -fno-optimize-sibling-calls")

In other projects we have:

  set(CMAKE_Fortran_FLAGS "-g -fno-range-check -funroll-loops ${CMAKE_Fortran_FLAGS}")
  set(CMAKE_Fortran_FLAGS_DEBUG "-ggdb -Wall")

So why all the extra settings in UFS_UTILS?

@GeorgeGayno-NOAA do you know?

[edwardhartnett]

Also we have these messages when CMake is run:

cc1: warning: command-line option ‘-fallow-invalid-boz’ is valid for Fortran but not for C
cc1: warning: command-line option ‘-fallow-argument-mismatch’ is valid for Fortran but not for C

[GeorgeGayno-NOAA]

Branch at 85902c3 successfully compiled in Debug mode on Orion, Jet, WCOSS2 (Intel only) and Hera (Gnu and Intel).