Skip to content

Add support for BF16 sbgemm on RISCV. #6084

Add support for BF16 sbgemm on RISCV.

Add support for BF16 sbgemm on RISCV. #6084

Triggered via pull request September 22, 2025 18:22
Status Success
Total duration 2h 24m 15s
Artifacts

dynamic_arch.yml

on: pull_request
neoverse_build
8m 3s
neoverse_build
Matrix: build
Matrix: cross_build
Matrix: msys2
Fit to window
Zoom out
Zoom in

Annotations

1 warning and 6 notices
build (ubuntu-latest, gfortran, make)
Failed to restore: "/usr/bin/tar" failed with error: The process '/usr/bin/tar' failed with exit code 2
msys2 (MINGW32, int32, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (CLANG64, int32, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (CLANG64, int64, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (UCRT64, int32, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (UCRT64, int32, None, mingw-w64-ucrt-x86_64, fc)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677
msys2 (UCRT64, int64, Release)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677