-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Release OpenBLAS 0.2.20 #1223
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
Comments
@xianyi Do you have an ETA for the 0.2.20 release? |
@boegel about Jul 15 |
I will correct PR1199 |
@xianyi as already noted in #1118 I would like to grab the fix for #1117 from wernsaar's fork as Werner appears to be unavailable. I also have a tentative fix for #1155 and I would appreciate your comment on #1137 (handling of unaligned accesses) but these can wait. Seeing that the 0.2.20 release date has been slipping since early march I'd really like to see it released rather sooner than later now, especially with the upcoming summer holidays in the northern hemisphere. (I know there is work underway on improving BLAS support for IBM z13 but it seems @quickwritereader is only about three quarters through at the moment, so this too should probably end up in 0.2.21) |
Arm soft abi support is the most awaited one due to new ndk version. I am glad to hear that it was solved. |
It looks like we can release a new version this week. |
Can you consider hard-to-debug crasher fix #1234 ? |
Thanks. |
I have committed a fix to disable the new ReLAPACK option (did not even expect that big PR to get merged before 0.2.20) so I think everything should be ready now. The other PRs I am currently creating can go in right after the release I think (the L1 misdetection fix should improve performance on the latest |
Is there an updated ETA? What is missing apart from the Changelog? Anything one can do to help? |
@pbregener I am working on changelog and release a new version. |
Great, thanks! 😄 |
@martin-frbg
We are going to release a new version. Any other works to be done?
The text was updated successfully, but these errors were encountered: