CL_INVALID_BUILD_OPTIONS (-43) when running tests on mesa

clMathLibraries / clBLAS

a software library containing BLAS functions written in OpenCL

Apache License 2.0

839 stars 240 forks source link

CL_INVALID_BUILD_OPTIONS (-43) when running tests on mesa #240

Closed anadon closed 8 years ago

anadon commented 8 years ago

https://gist.github.com/anadon/94f6857692b302473250

More mesa-clBLAS issues. Started fishing on the #dri-devel channel. Could you guys start testing on mesa?

pavanky commented 8 years ago

It is very likely a mesa bug rather than a clBLAS bug. We (arrayfire) test important clBLAS functionality on intel, AMD, nvidia, apple, pocl and beignet platforms. They pass our tests without a hitch.

anadon commented 8 years ago

Ok. I'll talk more to the mesa dev's. But adding mesa as a build target would be nice.

pavanky commented 8 years ago

I want to test arrayfire with mesa as well, but this bug is holding us back.

anadon commented 8 years ago

I wonder if what I'm seeing is related or different. I also have a bug where OpenCL is only detecting 1GB of my card's memory.

anadon commented 8 years ago

I'm seeing CAPS_DEBUG and DEBUG_2 as compile time guards for debug code. What should I be using in src/library/blas/generic/commin2.cc between line 87 and 88 for checking makeKernel error states set by "storeErrorCode()"?

anadon commented 8 years ago

Is there a parallel to getErrorString proposed here http://stackoverflow.com/questions/24326432/convenient-way-to-show-opencl-error-codes ? Grep isn't leading me to anything offhand.