Ronan Keryell

Do you mean in the implementation of triSYCL `cl::sycl::kernel` or in the examples? This was changed in the specification to avoid the implementation to cache some relations between program/kernel/context... that...

OK, thank you for the clarification. Good remarks! In triSYCL implementation, there is lazy construction of OpenCL wrappers such as `cl::sycl::context` and caching of them once we get them. So...

It looks like the member function to copy between an accessor and a host pointer is not implemented yet... :-(

@j-stephan thank you for the clarification. The main problem for us is that Vitis is still based on an old version of Clang/LLVM which renders things quite difficult. I should...

Yes this is long, but keep in mind that anyway this is a research project that might work sometimes and has nothing in common with a supported product. :-) And...

There is a new article describing the project: https://hgpu.org/?p=24496

You could also use properties added to the kernel type or lambda, using a similar approach to https://github.com/executors/executors/blob/master/properties.md So you do not have to change the API using the kernels...

Interesting... Right timing: I am just fixing most of the current warnings I have in triSYCL but I have never seen this one... It looks like it has been deprecated...

I think it is unrelated to the architecture. Just that nobody tried with the latest Boost version like you. I will have the problem anyway in 2 days when Ubuntu...

Now that https://github.com/triSYCL/triSYCL/pull/309 has landed, I hope this is fixed. At some point we should have our CI running on ARM64.