-
Notifications
You must be signed in to change notification settings - Fork 238
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
OpenCL Error -11 in line163 of clBLAS/src/library/blas/xgemm.cc #205
Comments
@akshayc11 Can you check if this happens in the develop branch ? |
This does not happen with the develop branch. Thanks Akshay |
There is an additional issue when I move to develop. Some of the gemm calls return matrixes with nans, which do not appear if I revert back to the commit version that I had used before: commit 9731ea2 |
@akshayc11 Is this for complex gemm ? If so check out my PR. It has a fix for that. |
This is the PR I am referring to: #202 |
Its for gemm with real numbers only.. I am pretty sure the code I am running never deals with complex numbers. |
@akshayc11 Any chance you can link a stand alone snippet that reproduces the problem ? I am investigating other issues with clBLAS that we face when building with our library. I'll look into fixing this alongside the other issues. |
@pavanky Sorry for the delayed response. Unfortunately, I do not have a stand-alone snippet at this point. The code-base where I use this is quite convoluted and has multiple nested function calls before reaching the gemm call. For now, I have reverted back to a version of master that did work before. The following is with the clBLAS library using the develop branch When I try to run the sample code, I get the following:
|
On running the command with valgrind, I get:
|
Similar to
#172
I have been facing this issue on an Ubuntu 14.04 machine with NVIDIA Geforce Titan with cuda-7.5
This code used to work for me before the AutoGemm overhaul, but the latest iteration does not. It happens during the first call to the function itself.
Please let me know if you need any additional information.
I have been unsuccessful in compiling the test cases, so I cannot verify that the error is reproducible.
Thanks
Akshay
The text was updated successfully, but these errors were encountered: