Joachim Meyer

Hi Pekka, using Open SYCL/hipSYCL/AdaptiveCPP with clang built with assertations is currently unsupported, due to how the annotation of the device code is done in the frontend plugin. So set...

I believe this is an LLVM / ROCm version incompatibility issue. SSCP deals with this by removing the PICLevel metadata (-: What is the version reported by `/opt/rocm-5.5.0/llvm/bin/clang++ --version` ?...

Hmm.. gives me the bad feeling our workaround for https://github.com/llvm/llvm-project/issues/68120 just moved the problem from compile to runtime..?

Jup, don't mix Debug and Release on windows, they have different abi and when linking normally (I.e. not at runtime), you will be notified about this by erroring out with...

https://github.com/AdaptiveCpp/AdaptiveCpp/pull/778/files Was looked at for known identity iirc

If you actually cross compile AdaptiveCpp for risc-v already, the clang plugin will be risc-v built as well, thus cannot be loaded on your x86 machine.. The current build system...

In most compilation flows (except library only openmp and nvc++) AdaptiveCpp uses your system clang for compiling host as well as device code. So, in theory almost everything that this...

With USM pointers you need to ensure the submissions are synchronized by one of two means: use `handler::depends_on` on the event returned by the memcpy or use in order queues....

This is normal C++ semantics of capturing objects in a lambda not by reference (which is not possible for kernels). The captured object will always be `const`. In theory one...

Hmm.. I think the current openmp back end always assumes shared memory between the "host" and the CPU device.. So querying if it's the omp backend should be fine. I...