Alfio Lazzaro

> gfortran links with the runtime included in the gcc distribution. I do not know if it is possible to change it. Clang might offer the possibility to switch between...

According to the [CUDA description:](https://docs.nvidia.com/cuda/cuda-runtime-api/group__CUDART__DEVICE.html#group__CUDART__DEVICE_1g05956f16eaa47ef3a4efee84563ccb7d) > cudaLimitPrintfFifoSize controls the size in bytes of the shared FIFO used by the printf() device system call. Setting cudaLimitPrintfFifoSize must not be performed after...

> I do not understand it either, I have simply not root-caused the issue let alone reporting the software versions like CUDA (or HPCSDK). I am currently retrying with [this](https://github.com/hfp/dbcsr/commit/c002658a71da77db897ba3e63fba973dfebc8f8b)...

Let's leave this ticket open... I think the issue here is when the RT fails to build a kernel, but I'm not sure...

(Taking over from https://github.com/cp2k/dbcsr/pull/777#issuecomment-2059160289) > > I think we can move the call to a more convenient place... > > What do you suggest? Putting it into acc_init may not...

We never tested such old versions of OSX, so I have no idea what the error can be. Some notes: 1. From your log, it seems you are not running...

This was my suspicious, on OSX we allow assume that Accelerate is used... I will try to install a vagrant machine with OSX and try to fix this problem when...

> > This was my suspicious, on OSX we allow assume that Accelerate is used... I will try to install a vagrant machine with OSX and try to fix this...

So, could you run the tests via ``` env CTEST_OUTPUT_ON_FAILURE=1 make test ARGS="--timeout 2000" ``` ? I'm guessing, I really need to reproduce it on my side...

I've realized that we are not testing with MPI_F08 in our CI, however we did a test here https://github.com/cp2k/dbcsr/issues/661#issuecomment-1621787249 and it worked. the only difference was GCC 13.1. I will...