-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Comments
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 ? |
In |
uh-oh, there is a stray "1" in kernel/setparam-ref.c as a leftover from the initial placement of the "align_k".... |
Maybe (wild guess) related to: #3801? |
I will try to test this PR with scipy later this evening. |
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 |
I can confirm, that with Remove excess initializer (leftover from rework of PR 3793) scipy.test() is running without failures and segfaults again. |
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.
The text was updated successfully, but these errors were encountered: