-
-
Notifications
You must be signed in to change notification settings - Fork 452
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
openblas 0.3.6 #27847
Comments
This comment has been minimized.
This comment has been minimized.
Branch: u/vbraun/openblas_0_3_6 |
Author: Volker Braun |
Commit: |
New commits:
|
comment:4
these patches you removed - they are upstream, or they just don't apply? |
comment:5
Upstreamed |
Reviewer: Dima Pasechnik |
comment:6
OK, so Cygwin should not be a problem then. |
comment:7
On Gentoo Linux withg gcc 9.1 I am getting here from
as well as
and one more polybori-related failure, in total 3
|
comment:8
Yes, see #27676 for the brial failures with gcc9 |
comment:9
anyhow, I also tested with gcc 8.3 on Linux and on OSX with clang, these are all good. |
This comment has been minimized.
This comment has been minimized.
comment:10
This new version also fixes a compile problem unrelated to #27676 that I encountered with 0.3.5.p1, on a CentOS Linux release 7.6.1810 running on Intel(R) Xeon(R) Gold 6152 CPU. 0.3.6 from this ticket compiles and passes its test suite on this system. |
comment:11
while we are at it, can we drop |
comment:12
Replying to @dimpase:
In fact, I don't know where |
New commits:
|
Changed branch from u/vbraun/openblas_0_3_6 to public/packages/openblas_0_3_6 |
comment:14
OK, I see there is a small problem - one still needs to make these |
comment:15
Let us postpone this then, so back to postive review from me. |
Changed branch from public/packages/openblas_0_3_6 to u/vbraun/openblas_0_3_6 |
comment:16
I'll give it a look. I want to review this very carefully, as I've been practically traumatized by OpenBLAS in the last year. I know this release should include many of my existing fixes but I want to look over the other diffs between versions to make sure no other obvious regressions crept in. |
comment:17
Can you do this sometime soon, I can't build Sage on my own PC... |
comment:18
How crucial is Openblas for Cygwin? Can't one use SAGE_ATLAS_LIB and whatever is supplied by Cygwin? (but we should work on #27870 anyway, to resolve these things in a meaningful way) |
comment:19
Any updates? |
comment:20
Replying to @vbraun:
|
comment:21
I will test this as soon as I can get a working Sage, which now seems to be a problem due to some other reason (possibly related to #27901 but unclear). |
comment:23
That I'm on gcc9 and while I can technically build Sage, the testsuite fails with heaps of errors. I'm in favor of releasing this if Eric can't try out cygwin any time soon. Its a must fix for currently supported platforms. |
comment:24
Replying to @vbraun:
+1 |
comment:25
On a different Linux system (Ubuntu 18.04.2 LTS, running on some virtualized AMD system), I have the following problem with both 0.3.5.p1 and 0.3.6:
Nevertheless, I'm setting the ticket to positive review. |
Changed reviewer from Dima Pasechnik to Dima Pasechnik, Matthias Koeppe |
comment:27
What exactly is the issue with gcc9 that this is resolving? |
Changed branch from u/vbraun/openblas_0_3_6 to |
comment:30
Replying to @dimpase:
I think not being able to use the most bleeding-edge version of a compiler is not such a blocker if it means forcing dependency updates that could lead to instabilities in other ways (in general being always at the bleeding edge lends some instability; as does falling too far behind). In this case, at least, I haven't been able to identify any major problems with this openblas release, and it fixes all the problems i'm aware of from 0.3.5, which was a mess. |
Changed commit from |
comment:31
This seems to cause Sage to crash with some machines using OS X. From the end of Sage_crash_report.txt:
|
comment:32
Followup at #27961. |
comment:33
why does the error message mention 0.3.5 as the version number of the library which cannot be loaded? and not 0.3.6? |
comment:34
I don't know, but that's the error I get with this ticket plus 8.8.beta7, incremental build. |
comment:35
A second issue, only present on one OS X machine so far:
This occurs with 8.8.beta7 + this ticket. For now, let's track both issues at #27961. If they need to be separated into two tickets, we can do this later. |
CC: @embray
Component: packages: standard
Author: Volker Braun
Branch:
26ce230
Reviewer: Dima Pasechnik, Matthias Koeppe
Issue created by migration from https://trac.sagemath.org/ticket/27847
The text was updated successfully, but these errors were encountered: