(libgpuarray maintainer) This isn't testable in a qemu-armhf chroot, as pocl doesn't work there.
Do all the non-clblas tests pass? (This can be checked by uninstalling libclblas-dev then running the tests - this will "error" the clblas tests but should at least not crash them.)
On 19/11/2020 14:39, Andreas Beckmann wrote:
It terminates with a segmentation fault in LLVM.
This is potentially an *LLVM* bug, as invalid input source code shouldn't crash the compiler, but that's less clear-cut when the compiler is being called as a library.
If it is, it doesn't seem to be known: there are no upstream LLVM bugs with this backtrace.
The CL kernel is a piece of generated source code created by the (simplified) stack: python - libgpuarray - libclblas before it gets handed over to pocl. While I managed to extract the CL kernel source, I
That's as expected. Can you post this kernel source here?
#0 getEmissionKind () at /build/llvm-toolchain-10-hVI0Qp/llvm-toolchain-10-10.0.1/llvm/include/llvm/IR/DebugInfoMetadata.h:1244 #1 initialize () at /build/llvm-toolchain-10-hVI0Qp/llvm-toolchain-10-10.0.1/llvm/lib/CodeGen/LexicalScopes.cpp:53
Did you have libllvm10-dbgsym installed? If not, does installing that give a more detailed backtrace? (I suspect an invalid 'this', given that the crashing line accesses only a class member.)
