diff options
| author | aidanfnv <aidanf@nvidia.com> | 2025-10-07 01:56:23 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-10-07 08:56:23 +0000 |
| commit | 0dac20642b971191256e058282811cf9307292e7 (patch) | |
| tree | 3a72079596da4e1406c52f44480292be86038340 /tests/optimization | |
| parent | 36ed0362dcfe6a40570beb12c78d24c00ab051d6 (diff) | |
Use GitHub runners for Windows releases, disable CUDA for aarch64 (#8613)
For #8596
Fixes #8597
This switches our release workflow back to using GitHub's
`windows-latest` runners, which we were using previously.
It also adds the variable `extra-cmake-flags` to the `windows-aarch64`
entry in the workflow's matrix with the value `"-DSLANG_ENABLE_CUDA=0"`.
If we are cross-compiling aarch64 on x86_64, and the x86_64 CUDA Toolkit
is installed, it will be auto-detected by cmake and the build will fail
(no aarch64 version of CUDA Toolkit exists).
The `windows-latest` runners do not have CUDA Toolkit, so they do not
encounter this issue, but if we do end up building on runners that do
(such as the temporary move to self-hosted runners), adding that flag
eliminates that potential problem.
This release workflow does build properly on `windows-latest` with
`extra-cmake-flags`:
https://github.com/aidanfnv/slang/actions/runs/18293521738
Diffstat (limited to 'tests/optimization')
0 files changed, 0 insertions, 0 deletions