Comparison of build configurations between CABLE-POP_TRENDY and main

[SeanBryan51]

Context:

• We want to consolidate the build systems across CABLE to use the latest build system with CMake to improve ease of testing with tools such as benchcab and spack.
• With the current CABLE-4 development around CABLE-POP_TRENDY, it makes sense to port this branch first.

This issue thread documents the differences in build configurations between CABLE-POP_TRENDY and main.

Useful links

• See the latest build script and Makefile for CABLE-POP_TRENDY.
• See deprecated build script and Makefile for MPI applications in CABLE-POP_TRENDY.

[SeanBryan51]

Differences in build configs in CABLE-POP_TRENDY:

• Uses GNU Make
• Support for multiple machines:
  • gadi.nci.org.au
  • pearcey.hpsc.csiro.au
  • MatthiasCuntz@INRAE
  • ...
• Gadi specific differences:
  • Supports only the Intel compiler.
  • Intel LLVM compiler module used: intel-compiler-llvm/2023.0.0
  • NetCDF: netcdf/4.9.2
  • Compiler flags for release configuration: -fpp -O3 -nofixed -assume byterecl -fp-model precise -ip -diag-disable=10382,15009 -march=broadwell -axSKYLAKE-AVX512,CASCADELAKE,SAPPHIRERAPIDS -D__INTEL__ -D__INTEL_COMPILER__ -D__NETCDF3__
• Matthias's configuration (host_mcin) differences:
  • Multiple compilers supported: Intel (classic), GNU, NAG
  • Compiler flags for release configuration for Intel compiler: -fpp -O3 -nofixed -assume byterecl -fp-model precise -ip -diag-disable=10382 -xHost -D__INTEL__ -D__INTEL_COMPILER__ -D__CRU2017__ -D__NETCDF3__ -D__C13DEBUG__
  • Compiler flags for debug configuration for Intel compiler: -fpp -O0 -debug extended -traceback -g -check all,noarg_temp_created -warn all -fp-stack-check -nofixed -assume byterecl -fp-model precise -diag-disable=10382 -fpe0" # -fpe-all=0 -no-ftz -ftrapuv -init=arrays,snan -D__INTEL__ -D__INTEL_COMPILER__ -D__CRU2017__ -D__NETCDF3__ -D__C13DEBUG__
  • Compiler flags for release configuration for GNU compiler (Note - most of these flags were adopted in the main branch): -cpp -O3 -Wno-aggressive-loop-optimizations -ffree-form -ffixed-line-length-132 -march=native -D__GFORTRAN__ -D__gFortran__ -D__CRU2017__ -D__NETCDF3__ -D__C13DEBUG__
  • Compiler flags for debug configuration for GNU compiler (Note - most of these flags were adopted in the main branch): -cpp -O -g -pedantic-errors -Wall -W -Wno-maybe-uninitialized -ffree-form -ffixed-line-length-132 -fbacktrace -ffpe-trap=zero,overflow -finit-real=nan" # -ffpe-trap=zero,overflow,underflow -D__GFORTRAN__ -D__gFortran__ -D__CRU2017__ -D__NETCDF3__ -D__C13DEBUG__
  • Compiler flags for release configuration for NAG compiler: -O4 -fpp -colour -unsharedf95 -ideclient -ieee=full -free -not_openmp -mismatch -mdir . -march=native -D__NAG__ -ideclient -unsharedrts -D__CRU2017__ -D__NETCDF3__ -D__C13DEBUG__
  • Compiler flags for debug configuration for NAG compiler: -C=alias -C=array -C=bits -C=dangling -C=do -C=intovf -C=present -C=pointer -C=recursion -g -nan -O0 -strict95 -gline -fpp -colour -unsharedf95 -ideclient -ieee=full -free -not_openmp -mismatch -mdir . -march=native -D__NAG__ -ideclient -unsharedrts -D__CRU2017__ -D__NETCDF3__ -D__C13DEBUG__
• Matthias's configuration (host_mc16) differences:
  • Multiple compilers supported: GNU, NAG
  • Compiler flags look mostly the same as other cases.
• Matthias's configuration (host_mcmi) differences:
  • Multiple compilers supported: GNU, NAG
  • Compiler flags look mostly the same as other cases.
• Matthias's configuration (host_vm_o) differences:
  • Multiple compilers supported: Intel (classic), GNU
  • Compiler flags look mostly the same as other cases.
• Matthias's configuration (host_logi) differences:
  • Multiple compilers supported: Intel (classic), GNU
  • Compiler flags look mostly the same as other cases.
• Lars Nieradzik @ aurora.lunarc.lu.se (host_auro) differences:
  • Only Intel compiler supported.
  • Compiler flags look mostly the same as other cases.
• Zihan's PC (host_zlle) differences:
  • Only GNU compiler supported.
  • Compiler flags look mostly the same as other cases.
  • ld flags: -Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -Wl,-z,relro -Wl,-z,now

Differences in build configs in CABLE-POP_TRENDY (MPI):

• Similar structure to build script for serial application.
• Gadi specific differences:
  • MPI libraries: intel-mpi/2021.5.1
  • MPI compiler wrapper: mpiifort
  • NetCDF: netcdf/4.8.0
  • Compiler flags for release configuration: -fpp -O3 -nofixed -assume byterecl -fp-model precise -ip -diag-disable=10382 -xCASCADELAKE -xCORE-AVX2 -axSKYLAKE-AVX512,CASCADELAKE -xBROADWELL -xSKYLAKE -D__INTEL__ -D__INTEL_COMPILER__ -D__MPI__ -D__CRU2020__ -D__NETCDF3__
  • Compiler flags for debug configuration: -fpp -O0 -debug extended -traceback -g -check all,noarg_temp_created -warn all -fp-stack-check -nofixed -assume byterecl -fp-model precise -diag-disable=10382 -fpe0 -fpe-all=0 -no-ftz -ftrapuv -D__INTEL__ -D__INTEL_COMPILER__ -D__MPI__ -D__CRU2020__ -D__NETCDF3__

[JhanSrbinovsky]

I haven't used the new build system yet. With "CABLE4" to date I have been modifying the CABLE3-like build/Makefile (albeit the one from the CABLE-POP-TRENDY side [so it is very similar to the CABLE3 build3.sh (and Makefile) version - just older]). My estimation was that upon completion the Makefile etc would look just like the CABLE3 ones you have just done. BUT the CABLE4 I "was" doing has no overlap with offline applications so will need some extra bits to build with POP offline.

WRT to all the user/machine profiles. In the beginning we tried to cater for everyone. We then went to a self writing build script to include new profiles. It just got really messy. In the end we landed on:

"We support the use of CABLE (corresponding builds etc) at NCI. We are happy to help with alternatives, but really this is on you. "

[SeanBryan51]

@JhanSrbinovsky in the case for compiling on Gadi, the Makefile build in CABLE-POP_TRENDY branch differs in compiler flags for debug/release configurations as well as module versions for dependencies. We should determine the differences that should be incorporated/discarded when we do the merge of CABLE-POP_TRENDY into main.