You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This could be lifted by removing the -march=native option used to compile testvecabi, that was clashing with the -mavx512f option used to compile routines.
Should we re-enable this feature and fix issue with ABI uncovered by -march=native?
The text was updated successfully, but these errors were encountered:
)
* Add CI on Github Actions for x86_64, aarch64, armhf, ppc64 and s390x
* Disable -march=native for testervecabi - fails when compiling on a host CPU with AVX512f (#478)
* Enable qemu features for s390x, ppc64, and arm
* Add some architecture-specific cmake flags
* Use job dependencies to avoid duplicating building native
* Fix permissions in downloaded artifacts
* Disable arm inline headers - don't work (#480)
* Document why DISABLE_VXE2 on s390x
It was pointed out in #476 that x86 build of testvecabi was failing due to a mismatch in CPU features.
https://github.com/rivosinc/sleef/actions/runs/6753516221/job/18360067282
This could be lifted by removing the
-march=native
option used to compile testvecabi, that was clashing with the-mavx512f
option used to compile routines.Should we re-enable this feature and fix issue with ABI uncovered by
-march=native
?The text was updated successfully, but these errors were encountered: