-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Access violation on 64-bit Windows when using LAPACKE_dgesv #214
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
Hi @beagle2011 Thank you for the feedback. Please upload the test code to gist.github.com or send me email traits.zhang at gmail.com Xianyi |
Hi @xianyi, |
@beagle2011 , Xianyi |
Thanks @xianyi. On a side note, I just run the DGESV benchmark on Linux (1 right-hand side, varying n), and it turns out OpenBLAS is outperforming the latest version of MKL by a significant margin on my system, especially from n >= 2048. Congrats! There is also a small advantage at small matrix sizes (not visible from the plot), which is I suppose might be due to dynamic dispatching in MKL versus static dispatching in OpenBLAS. |
Hi @beagle2011 , Did you try the single thread OpenBLAS in VS 2012? For example, export OPENBLAS_NUM_THREADS=1 Xianyi |
Hi @xianyi, |
Hi @beagle2011 , How many CPU cores on your windows box? Xianyi |
Hi @xianyi, Thanks |
Dear xianyi,
first, I would like to thank you for your useful work on OpenBLAS. Unfortunately, I encountered an issue on 64-bit Windows 8.
When calling LAPACKE_dgesv from a C++ program compiled with Visual Studio 2012, I encounter the following error:
"Unhandled exception at 0x000000006CCAD850 (libopenblas.dll) in TestOpenBLAS.exe: 0xC0000005: Access violation writing location 0x00000000C55F4000."
When I compile the same program with g++, no access violation occurs, however, I noticed that some computations after the call yield an incorrect result, probably suggesting a corrupted stack.
On Linux, the same code runs cleanly under valgrind. Moreover, sgemm and dgemm and seem to work fine on both Linux and Windows.
If you have the to investigate this issue, I will send you the source code.
PS The issue occurs with both OpenBLAS 0.2.6 and the develop branch.
The text was updated successfully, but these errors were encountered: