Tobias Ribizel
Tobias Ribizel
Indeed, it seems like the `MPIEXEC_EXECUTABLE` variable is empty when setting up the tests. I see you are specifying it as part of your CMake invocation, is it then properly...
Another useful feature might be the `environment` object, with which we can configure path-independent `CXX` and `CUDACXX` compiler executable names
I could imagine `develop-clang` being useful from time to time, especially with its better diagnostics
@pratikvn I think the issue there is that they depend on loaded modules, and the executable names (gcc etc) are the same otherwise, so the configs may not help and...
I think what's likely happening here is that while we guard against NaNs/Infs in our asynchronous sweep, they may still come up in the other operations, e.g. from an overflowing...
That is a CMake issue, we are relying on the FindOpenMP module. Can you compile a small OpenMP test program successfully? As a workaround, you can specify the `OpenMP_C(XX)_FLAGS`, `OpenMP_C(XX)_LIB_NAMES`...
We don't do anything unusual for OpenMP detection, this is the standard CMake way of enabling it. Does a simple ``` project(Test LANGUAGES C CXX) find_package(OpenMP 3.0 REQUIRED) ``` work...
label!
I've decided the complexity involved in sub-devices just to get #1373 working on SYCL CPUs isn't worth it yet, so I'll be removing those changes, only fixing the deprecation warnings
How did you determine the affected versions? It looks like they still use wavefronts of 64 threads, so there might be something going wrong with the macro we use to...