Jan Stephan

Apparently this has been fixed in GCC. The following configuration compiled on my local system with GCC 12.2: ``` cmake .. -Dalpaka_CXX_STANDARD=17 -DBUILD_TESTING=ON -Dalpaka_ACC_ANY_BT_OACC_ENABLE=ON -DCMAKE_BUILD_TYPE=Release ``` I also tested this...

Since alpaka is about being explicit: Maybe we should add alpaka "intrinsics" that emulate the behavior of `__ldg` and friends?

Intel has a SYCL extension for FPGAs called "load-store units". See [here](https://github.com/intel/llvm/blob/sycl/sycl/doc/extensions/supported/sycl_ext_intel_fpga_lsu.md). Maybe it would be worthwhile to copy the concept into alpaka where it could look like this: ```c++...

What is the state here?

Not right now, but I'm still for trying out `ExternalProject`. Shouldn't be that hard I think.

I just tried it with `FetchContent` which should be really similar to `ExternalProject`. The variables still show up in `ccmake` so feel free to try out your approach.

Yes, we've been on CMake 3.22 for a while.

Since we now have `mdspan` and have decided to abandon accessors we can close this PR, right?

> I don't think the distinction between copyright and contributor serves us. I believe it is quite important. Example: You are going to leave us in a few months. Now...

> Well, that's exactly an argument for me being the copyright holder. You can't just decide to become a copyright holder. > I was employed by CASUS for 3 months,...