240501.213307.HKT fix cmake.yml

opt4ai · May 1, 2024 · ae49b5a · ae49b5a
1 parent 1e5b743
commit ae49b5a
Showing 1 changed file with 22 additions and 22 deletions.
diff --git a/.github/workflows/cmake.yml b/.github/workflows/cmake.yml
@@ -51,12 +51,12 @@ jobs:
         # First define the toolchains on Linux and macOS.
         os: [ubuntu-latest, macos-12, macos-13]
         toolchain:
-          - {compiler: gcc, version: 11, cflags: ${{ env.GCC_FLAGS }}, fflags: ${{ env.GFORTRAN_FLAGS }}}
-          - {compiler: gcc, version: 12, cflags: ${{ env.GCC_FLAGS }}, fflags: ${{ env.GFORTRAN_FLAGS }}}
-          - {compiler: gcc, version: 13, cflags: ${{ env.GCC_FLAGS }}, fflags: ${{ env.GFORTRAN_FLAGS }}}
-          - {compiler: intel-classic, version: '2021.8', cflags: ${{ env.ICC_FLAGS }}, fflags: ${{ env.IFORT_FLAGS }}}
-          - {compiler: intel-classic, version: '2021.9', cflags: ${{ env.ICC_FLAGS }}, fflags: ${{ env.IFORT_FLAGS }}}
-          - {compiler: intel-classic, version: '2021.10', cflags: ${{ env.ICC_FLAGS }}, fflags: ${{ env.IFORT_FLAGS }}}
+          - {compiler: gcc, version: 11, cflags: "${{ env.GCC_FLAGS }}", fflags: "${{ env.GFORTRAN_FLAGS }}"}
+          - {compiler: gcc, version: 12, cflags: "${{ env.GCC_FLAGS }}", fflags: "${{ env.GFORTRAN_FLAGS }}"}
+          - {compiler: gcc, version: 13, cflags: "${{ env.GCC_FLAGS }}", fflags: "${{ env.GFORTRAN_FLAGS }}"}
+          - {compiler: intel-classic, version: '2021.8', cflags: "${{ env.ICC_FLAGS }", fflags: "${{ env.IFORT_FLAGS }"}
+          - {compiler: intel-classic, version: '2021.9', cflags: "${{ env.ICC_FLAGS }", fflags: "${{ env.IFORT_FLAGS }"}
+          - {compiler: intel-classic, version: '2021.10', cflags: "${{ env.ICC_FLAGS }", fflags: "${{ env.IFORT_FLAGS }"}
 
         include:
           # intel compiler (ifx) does not support macOS. So they are not included above but below.
@@ -65,41 +65,41 @@ jobs:
           # compiler, but the (new) intel c compiler does not recognize '-W3 -Werror-all', even though the
           # official documentation of the compiler mentions them. Why?
           - os: ubuntu-latest
-            toolchain: {compiler: intel, version: '2023.2', cflags: ${{ env.ICX_FLAGS }}, fflags: ${{ env.IFX_FLAGS }}}
+            toolchain: {compiler: intel, version: '2023.2', cflags: "${{ env.ICX_FLAGS }", fflags: "${{ env.IFX_FLAGS }"}
           - os: ubuntu-latest
-            toolchain: {compiler: intel, version: '2024.0', cflags: ${{ env.ICX_FLAGS }}, fflags: ${{ env.IFX_FLAGS }}}
+            toolchain: {compiler: intel, version: '2024.0', cflags: "${{ env.ICX_FLAGS }", fflags: "${{ env.IFX_FLAGS }"}
           - os: ubuntu-latest
-            toolchain: {compiler: intel, version: '2024.1', cflags: ${{ env.ICX_FLAGS }}, fflags: ${{ env.IFX_FLAGS }}}
+            toolchain: {compiler: intel, version: '2024.1', cflags: "${{ env.ICX_FLAGS }", fflags: "${{ env.IFX_FLAGS }"}
 
           # What follows contains the toolchains for Windows, including gcc, intel classic, and intel.
           - os: windows-latest
-            toolchain: {compiler: gcc, version: 11, cflags: ${{ env.GCC_FLAGS }}, fflags: ${{ env.GFORTRAN_FLAGS }}}
+            toolchain: {compiler: gcc, version: 11, cflags: "${{ env.GCC_FLAGS }}", fflags: "${{ env.GFORTRAN_FLAGS }}"}
           - os: windows-latest
-            toolchain: {compiler: gcc, version: 12, cflags: ${{ env.GCC_FLAGS }}, fflags: ${{ env.GFORTRAN_FLAGS }}}
+            toolchain: {compiler: gcc, version: 12, cflags: "${{ env.GCC_FLAGS }}", fflags: "${{ env.GFORTRAN_FLAGS }}"}
           - os: windows-latest
-            toolchain: {compiler: gcc, version: 13, cflags: ${{ env.GCC_FLAGS }}, fflags: ${{ env.GFORTRAN_FLAGS }}}
+            toolchain: {compiler: gcc, version: 13, cflags: "${{ env.GCC_FLAGS }}", fflags: "${{ env.GFORTRAN_FLAGS }}"}
           # Zaikun 20240423:
           # 1. On windows-latest, the cflags will not be recognized correctly if we start them with `/` instead
           # of `-`, even though the former aligns with the official documentation of the compilers. Why?
           # 2. On windows-latest, we want to use '-Wall -W5 -Werror-all' as what we do for the intel-classic
           # compiler, but the (new) intel c compiler does not recognize '-W5 -Werror-all', even though the
           # official documentation of the compiler mentions them. Why?
           - os: windows-latest
-            toolchain: {compiler: intel, version: '2023.2', cflags: ${{ env.ICX_FLAGS_WIN }}, fflags: ${{ env.IFX_FLAGS_WIN }}}
+            toolchain: {compiler: intel, version: '2023.2', cflags: "${{ env.ICX_FLAGS_WIN }", fflags: "${{ env.IFX_FLAGS_WIN }"}
           - os: windows-latest
-            toolchain: {compiler: intel, version: '2024.0', cflags: ${{ env.ICX_FLAGS_WIN }}, fflags: ${{ env.IFX_FLAGS_WIN }}}
+            toolchain: {compiler: intel, version: '2024.0', cflags: "${{ env.ICX_FLAGS_WIN }", fflags: "${{ env.IFX_FLAGS_WIN }"}
           - os: windows-latest
-            toolchain: {compiler: intel, version: '2024.1', cflags: ${{ env.ICX_FLAGS_WIN }}, fflags: ${{ env.IFX_FLAGS_WIN }}}
+            toolchain: {compiler: intel, version: '2024.1', cflags: "${{ env.ICX_FLAGS_WIN }", fflags: "${{ env.IFX_FLAGS_WIN }"}
           - os: windows-latest
-            toolchain: {compiler: intel, version: '2024.1', cflags:  ${{ env.CL_FLAGS }}, fflags: ${{ env.IFX_FLAGS_WIN }}, cc: cl}
+            toolchain: {compiler: intel, version: '2024.1', cflags:  "${{ env.CL_FLAGS }", fflags: "${{ env.IFX_FLAGS_WIN }", cc: cl}
           # N.B.: As of 20240401, setup-fortran fails constantly with windows-latest and intel-classic
           # 2021.8. Thus this combination is not included.
           - os: windows-latest
-            toolchain: {compiler: intel-classic, version: '2021.9', cflags: ${{ env.ICC_FLAGS_WIN }}, fflags: ${{ env.IFORT_FLAGS_WIN }}}
+            toolchain: {compiler: intel-classic, version: '2021.9', cflags: "${{ env.ICC_FLAGS_WIN }", fflags: "${{ env.IFORT_FLAGS_WIN }"}
           - os: windows-latest
-            toolchain: {compiler: intel-classic, version: '2021.10', cflags: ${{ env.ICC_FLAGS_WIN }}, fflags: ${{ env.IFORT_FLAGS_WIN }}}
+            toolchain: {compiler: intel-classic, version: '2021.10', cflags: "${{ env.ICC_FLAGS_WIN }", fflags: "${{ env.IFORT_FLAGS_WIN }"}
           - os: windows-latest
-            toolchain: {compiler: intel-classic, version: '2021.10', cflags: ${{ env.CL_FLAGS }}, fflags: ${{ env.IFORT_FLAGS_WIN }}, cc: cl}
+            toolchain: {compiler: intel-classic, version: '2021.10', cflags: "${{ env.CL_FLAGS }", fflags: "${{ env.IFORT_FLAGS_WIN }", cc: cl}
 
     steps:
 
@@ -190,9 +190,9 @@ jobs:
         toolchain:
           # Classic Flang family with -Mchkptr would fail. See https://forums.developer.nvidia.com/t/bug-in-nvfortran-with-mchkptr-for-unallocated-optional-arguments/223220
           # As of 20240220, aflang with -Mbounds would fail due to the bug at https://github.com/flang-compiler/flang/issues/1238
-          - {compiler: nvfortran, cflags: ${{ env.GCC_FLAGS }}, fflags: '-C -Wall -Wextra -Minform=warn -Mstandard -Mbounds -Mchkstk'}
-          - {compiler: flang, cflags: ${{ env.GCC_FLAGS }}, fflags: '-std=f2018 -pedantic -fimplicit-none -Werror'}
-          - {compiler: aflang, cflags: ${{ env.GCC_FLAGS }}, fflags: '-pedantic -Weverything -Wall -Wextra -Minform=warn -Mstandard'}
+          - {compiler: nvfortran, cflags: "${{ env.GCC_FLAGS }}", fflags: '-C -Wall -Wextra -Minform=warn -Mstandard -Mbounds -Mchkstk'}
+          - {compiler: flang, cflags: "${{ env.GCC_FLAGS }}", fflags: '-std=f2018 -pedantic -fimplicit-none -Werror'}
+          - {compiler: aflang, cflags: "${{ env.GCC_FLAGS }}", fflags: '-pedantic -Weverything -Wall -Wextra -Minform=warn -Mstandard'}
 
     steps: