Skip to content

ci: run the loong64 qemu lane with LASX, and require it - #67

Merged
tannevaled merged 2 commits into
mainfrom
ci/loong64-lasx-under-qemu
Oct 26, 2026
Merged

tannevaled merged 2 commits into
mainfrom
ci/loong64-lasx-under-qemu

Conversation

@tannevaled

@tannevaled tannevaled commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

The loong64 qemu lane now runs the LSX/LASX kernels.

The lane ran on qemu's default CPU, so the loong64 LSX/LASX kernels only ever took their scalar fallbacks in CI. ci.yml said as much. The riscv64 RVV kernels had the same gap until #66, and there it hid a real defect.

This PR:

  • sets QEMU_CPU=la464 on the loong64 lane (la464 has LSX and LASX);
  • sets NDARRAY_REQUIRE_LASX;
  • adds TestLASXWhenRequired, which fails when that variable is set and the CPU does not report LASX.

Result (first CI run of this PR): the lane printed running loong64 under qemu-loongarch64 (QEMU_CPU=la464). Both packages passed with the requirement set, so qemu-user reports LASX in AT_HWCAP, and every LSX/LASX kernel now runs in CI and passes.

The second commit corrects the two ci.yml comments that said the qemu lanes keep the scalar paths.

CI only, no library change, so no release.

🤖 Generated with Claude Code

tannevaled and others added 2 commits October 26, 2026 12:19
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tannevaled tannevaled changed the title ci: run the loong64 qemu lane with LASX (experiment) ci: run the loong64 qemu lane with LASX, and require it Oct 26, 2026
@tannevaled
tannevaled marked this pull request as ready for review October 26, 2026 11:31
@tannevaled
tannevaled merged commit 1040579 into main Oct 26, 2026
12 checks passed
@tannevaled
tannevaled deleted the ci/loong64-lasx-under-qemu branch October 26, 2026 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant