OpenBLAS

78 MB

Tree: 48698b2b1d

Author	SHA1	Message	Date
gxw	48698b2b1d	LoongArch64: Rename core Use microarchitecture name instead of meaningless strings to name the core, the legacy core is still retained. 1. Rename LOONGSONGENERIC to LA64_GENERIC 2. Rename LOONGSON3R5 to LA464 3. Rename LOONGSON2K1000 to LA264	1 year ago
guxiwei	1ca1bb829d	LoongArch64: Update QEMU Compile the community version of QEMU to support LSX/LASX extension instructions	1 year ago
gxw	d9e2db3735	CI: add openblas_utest_ext for c910v, mips64 and loongarch64	1 year ago
Martin Kroeker	0f648ebcd1	use alternate download for the CLFS cross-compiler package	1 year ago
Xiaotian Wu	d2f4f1b28a	CI: update toolchains for LoongArch64	1 year ago
Ralf Gommers	2418a20f1f	Cancel running CI jobs when new changes are pushed to a PR The `group` expression ensures that the cancel-in-progress behavior is to only cancel if a new commit is pushed to the PR for which the job is running, not other PRs. This is a fairly standard snippet, used also in CI jobs for NumPy and other projects.	1 year ago
Ralf Gommers	1d4ed20c2f	Add conditions to all CI jobs to only run on main repo by default This is a follow-up to gh-4271. At the moment, when a contributor pushes the latest `develop` to their own branch to bring their own fork in sync with `main`, or if they push another branch, this triggers 30 CI jobs to run. Most will complete silently and only burn CPU time unnecessarily. If there's a failure, this may result in unexpected failure notifications. And the AWS Graviton3 run won't complete at all and time out, since the Cirun hook will only work when triggered from the main repo.	1 year ago
gxw	211bb35dee	gh-actions: Adding DYNAMIC_ARCH test for LoongArch64	2 years ago
gxw	96bf226bca	gh-actions: Add loongarch64 CI	2 years ago

9 Commits (48698b2b1d575cd4e10b5667e9dc5bd2fca1cbf2)