Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pull latest changes from upstream #5

Merged
merged 6 commits into from
Jul 23, 2024

Conversation

Pencilcaseman
Copy link
Member

No description provided.

dimula73 and others added 6 commits May 28, 2024 21:09
Some CPU vulnerability mitigations may disable AVX functionality
on the hardware level via the XCR0 register. We should check that
manually to verify that OS actually allows us to use this feature.

See https://bugs.kde.org/show_bug.cgi?id=484622

Fix #1025
Ideally the patch CPU detection code should also check if the length
of SVE and RVV is actually supported by the current CPU implementation
(i.e. ZCR_Elx.LEN register for SVE and something else for RVV), but
I don't have such CPUs/emulators handy, so I cannot add such checks.

Given that xsimd::available_architectures().has() is a new feature
of XSIMD13 and the length check has never been present in XSIMD, this
bug is not a regression at least.

The patch also adds a unittest that reproduces the error the patch fixes
xsimd is header only library, so prefer arch-independed paths for cmake and
pkg-config.

References:
 * xtensor-stack/xtl@d877d94
 * xtensor-stack/xtensor@7738389
@Pencilcaseman Pencilcaseman merged commit dd930b6 into LibRapid:master Jul 23, 2024
1 of 59 checks passed
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.

None yet

4 participants