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

Segfaults with scipy/openblas since 4989e039a5 #3803

Closed
carlkl opened this issue Oct 31, 2022 · 7 comments · Fixed by #3804
Closed

Segfaults with scipy/openblas since 4989e039a5 #3803

carlkl opened this issue Oct 31, 2022 · 7 comments · Fixed by #3804

Comments

@carlkl
Copy link

carlkl commented Oct 31, 2022

Since 'Define SBGEMM_ALIGN_K for DYNAMIC_ARCH build' I get segfaults and failures with scipy.test() in the following setting:

OS: Windows 64-bit
Compiler: msys2 GCC-12
OpenBLAS: 4989e039a5
Python: vanilla CPython-3.10
Scipy: local scipy-meson build

No further examinations were carried out right now other than narrowing down the problem to the mentioned commit.

@martin-frbg
Copy link
Collaborator

Can you be more specific about your build please ? It seems surprising to me that this particular commit would cause segfaults (where?) on an unrelated platform - do the scipy tests even use bfloat16 ?

@carlkl
Copy link
Author

carlkl commented Oct 31, 2022

In kernel/setparam-ref.c the parameter align_k was removed, and this is related to a Windows DYNAMIC_ARCH build, maybe by accident, in this commit.

@martin-frbg
Copy link
Collaborator

uh-oh, there is a stray "1" in kernel/setparam-ref.c as a leftover from the initial placement of the "align_k"....

@carlkl
Copy link
Author

carlkl commented Oct 31, 2022

Maybe (wild guess) related to: #3801?

@carlkl
Copy link
Author

carlkl commented Oct 31, 2022

I will try to test this PR with scipy later this evening.

@martin-frbg
Copy link
Collaborator

unlikely to be related to 3801 as I only merged the "offending" PR yesterday while the (original) Julia ticket is a week old. (plus I don't think they use bleeding-edge builds in Julia, so more likely something to do with "recent" LAPACK 3.10.1 or a general (Windows-specific?) threading issue that only happened to be "felt" now

@carlkl
Copy link
Author

carlkl commented Oct 31, 2022

I can confirm, that with Remove excess initializer (leftover from rework of PR 3793) scipy.test() is running without failures and segfaults again.

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 a pull request may close this issue.

2 participants