Rafael Schouten

I guess you would still call `eachtablerow` for those, and it would just be the defaults.

I'm not totally sure, was hoping it was on the (somewhat meagre) GPU! Two driver versions show up on my setup: ```julia OpenCL.Device(Intel(R) HD Graphics on Intel(R) OpenCL @0x000055ad4d6cb990) OpenCL.Device(Intel(R)...

I'm mostly trying to test that OpenCL will actually run the kernels that I was running on regular CPU. The main GPU work will be on CUDA, which I'm just...

Unfortunately not so easy! What would I be aiming for - padding it out to 64bit multiples? I'm also wondering if there is a long term solution for this, as...

Oh god I didn't realise it was like that... these are both Intel HD cards... ```julia julia> using CLArrays julia> CLArrays.init(CLArrays.devices()[2]) OpenCL context with: CL version: OpenCL 1.2 beignet 1.3...

Could it be beignet? devices [1] actually just segfaults on that last line. Or some other compiler version issue? I'm on arch linux so occasionally get bitten by bleeding edge...

For my Intel HD 5500 the simple demo above fails with the error shown, or a segfault, depending on the driver I select, as for some reason there is two....

Anyway, thanks @SimonDanisch for all your work on these things, especially now I know what a mess you have to deal with behind the scenes!!!

Yeah that's the same behaviour I'm seeing, the simple case works fine but a struct or tuple gives that error. I haven't tried it on an opencl CPU, but it's...

Building the CLArray is totally fine: ```julia CLArray([WithTuple(1, (2,3))]) GPU: 1-element Array{WithTuple,1}: WithTuple(1, (2, 3)) ```