Part of epic #165. The release matrix builds native binaries for macOS arm64, Linux x64/arm64 and Windows x64, but windows-arm64 has no native Fortran toolchain: MSYS2 CLANGARM64 ships clang (no gcc-fortran), and LLVM flang does not compile amica15's legacy F90 (needs -std=legacy/-fallow-argument-mismatch, which flang lacks). The workflow keeps windows-arm64 as an experimental (continue-on-error) job so it lights up automatically if a toolchain lands.
Interim: Windows 11 ARM runs x64 binaries via emulation, so the Phase 3 (#168) binary resolver maps windows-arm64 -> the windows-x64 asset. That covers Windows-ARM users functionally at an emulation performance cost.
Acceptance
- A native windows-arm64 binary built and smoke-tested in CI (via a working gfortran-for-aarch64 MSYS2 package if/when available, or a flang build path with the source adjustments flang needs), attached to the release.
- Resolver prefers the native arm64 asset over x64-emulation once it exists.
Part of epic #165. The release matrix builds native binaries for macOS arm64, Linux x64/arm64 and Windows x64, but windows-arm64 has no native Fortran toolchain: MSYS2 CLANGARM64 ships clang (no
gcc-fortran), and LLVM flang does not compile amica15's legacy F90 (needs-std=legacy/-fallow-argument-mismatch, which flang lacks). The workflow keeps windows-arm64 as an experimental (continue-on-error) job so it lights up automatically if a toolchain lands.Interim: Windows 11 ARM runs x64 binaries via emulation, so the Phase 3 (#168) binary resolver maps windows-arm64 -> the windows-x64 asset. That covers Windows-ARM users functionally at an emulation performance cost.
Acceptance