-
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
Stack overflow with openblas 0.3.26 against LAPACK 3.11 test suite #4574
Comments
Which compiler ? And can you work around it by supplying a larger /STACK: size to the linker ? Reference-LAPACK/lapack#987 is somewhat related (though the stack requirements supposedly were fixed in the LAPACK testsuite 3 years ago, and the CLAPACK that issue was raised against is ancient). Possibly some new test with huge static arrays may have crept in again after LAPACK 3.10, but you should be seeing the exact same problem with Reference-LAPACK |
more to the point, this should have been addressed by #4088 from 0.3.24 (copying Reference-LAPACK/lapack#854) |
Of course the original Reference-LAPACK PR only made it into their 3.12.0 release, so if you are actually mixing a NO_LAPACK=1 OpenBLAS with your own build of an unpatched 3.11.0 Reference-LAPACK , you will still get this and other since-resolved LAPACK errors. (But then you should probably be looking at the issue tracker for Reference-LAPACK anyway, instead of putting that here.) |
In my defense, all builds in conda-forge/blas-feedstock#114 are running the same unpatched LAPACK test suite, and only openblas + windows showed this failure (MKL failed even earlier for unrelated reasons). After backporting Reference-LAPACK/lapack#854, things work now, thanks a lot! 🙏 I'll make a point to double-check the lapack repo for related issues in the future. |
In conda-forge, we've been blocked for a long time from enabling newer LAPACK versions by default by failing tests in the LAPACK 3.10.1 test suite when run against MKL.
In the context of figuring out these errors, the Intel people asked me if it's possible to test against 3.11.0 as well, which I did in conda-forge/blas-feedstock#114. Through this, I noticed that there are failures with openblas builds on windows (while linux/osx run fine):
more detailed logs
The text was updated successfully, but these errors were encountered: