-
-
Notifications
You must be signed in to change notification settings - Fork 570
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
Fix segfault / memory corruption in OpenBLAS #27565
Comments
Commit: |
Branch: u/embray/ticket-27565 |
Author: Erik Bray |
comment:2
There is no changes to openblas on this branch. Did you forget to commit? |
comment:3
Strange. It looks like I did. |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:5
There it is. I was working on this on the train last week so who knows what could've interrupted me. |
comment:6
Including a a patch merged upstream. I think it is safe. |
Reviewer: François Bissey |
Branch pushed to git repo; I updated commit sha1 and set ticket back to needs_review. This was a forced push. New commits:
|
comment:8
Rebased on 8.8.beta0 (not strictly necessary, but I wanted to anyways so that I could test the rest of 8.8.beta0 on Cygwin). |
Changed commit from |
Changed branch from u/embray/ticket-27565 to |
comment:10
The branch on this didn't get updated for some reason. |
There is a bug in OpenBLAS already fixed upstream which I am encountering on Cygwin, though it could also affect Linux (in fact the original bug report was for Linux).
For Sage, this bug is causing a segfault on Cygwin when running
but it could happen arbitrarily anywhere that uses OpenBLAS and that happens to use threads (even without using OpenBLAS threads).
I have already confirmed that the upstream fix resolves the issue for me.
Upstream: Fixed upstream, but not in a stable release.
Component: packages: standard
Keywords: openblas
Author: Erik Bray
Branch:
4aa19b0
Reviewer: François Bissey
Issue created by migration from https://trac.sagemath.org/ticket/27565
The text was updated successfully, but these errors were encountered: