-
-
Notifications
You must be signed in to change notification settings - Fork 202
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
Segfaults with double precision tuning on Fiji #107
Comments
Are you testing on the |
I was testing on |
I don't know if the errors I get tuning the Xgemm with double precision are related to the above mentioned problem, but I will post it here first. [ FAILED ] Kernel Xgemm failed [ FAILED ] Xgemm; 0.0 ms; MWG 32; NWG 128; KWG 32; MDIMC 16; NDIMC 16; MDIMA 32; NDIMB 16; KWI 2; VWM 1; VWN 4; STRM 0; STRN 1; SA 1; SB 1;PRECISION 64; Maybe it is related to the driver but compared with the version above my version is: There is one thread related to this error at the khronos forums. |
Is this still an issue with the latest AMD compilers? And do you think it is related to CLBlast at all? |
I haven't seen updates to catalyst, so this should still be true. |
In this thread clMathLibraries/clBLAS#207 there is a solution to the issue you are describing. I managed to get thinks working after linking against libOpenCL provided by the driver NOT by the AMD APP. |
@MigMuc libOpenCL is currently only being provided by AMDAPP on my machine. It looks like the bug for clMathLibraries/clBLAS#207 has something to do with multiple CPU threads ? @CNugteren Yes, this should definitely be AMDs task to fix; feel free to close this (or perhaps add some archival flag). I'll try to dump the kernel that is causing this issue and file a bug report with AMD. |
Calling clblast_xgemm_tuner with
-platform 0 -device 0 -precision 64 (double) -m 1024 [=default] -n 1024 [=default] -k 1024 [=default] -alpha 2.000000 [=default] -beta 2.000000 [=default] -fraction 512.000000
results in a
SIGSEGV
. I think there was a issue that was filed earlier that indicated that the cause of such segfaults was to be found in the driver. I'm currently usingCatalyst 15.12
with a R9 Nano.The text was updated successfully, but these errors were encountered: