Benjamín Hernández

Just to clarify that the suggested flag, ```-mno-float128```, was not recognized by nvRTC/jitify, so it should be another flag. ``` $ python ../test.py Compiler options: -std=c++14 -remove-unused-globals -mno-float128 -w -D__CUDACC_RTC__...

It seems ppc64le support is enabled by ```__IBMCPP__``` as suggests line 113 of the next file https://github.com/ogiroux/libcxx/blob/36156f0962149ef19ce778110642150b456a182b/include/limits#L113 added that flag to Jitify compiler flags (.../cudf/cpp/src/jit/common_headers.hpp) : ``` const std::vector compiler_flags{...

Thanks, I recompiled using the CUDA 11.5 module available on Summit

Thanks for the clarification. I agree, if we disable access to `libcufile.so` we'll be in the safe place. I am supporting Rapids on Summit and I'd like to include cuCIM...

Btw, Is cuCIM not meant to be build within an existent built from source Rapids environment ? I noted cuCIM gets its own rmm and also uses its own dlpack...

Sounds nice, Recently I've been running the [cugraph benchmarks](https://github.com/rapidsai/cugraph/tree/branch-21.12/benchmarks/python_e2e) on Summit and as graph size goes up, there is a lot of these messages: ``` distributed.core - INFO - Event...

Hi @MordicusEtCubitus, In our case what we decided to do is to created a job script where the dask-scheduler and dask-cuda-workers are launched, then launch the python client. Note that...

PIConGPU came from the dev branch dated back to Nov. 2020 with its own Alpaka distribution ``` commit 84e03980f2a56c7aea24d88bc3be9eb43f1a3197 Merge: aa86f2d c5208f4 Author: Sergei Bastrakov Date: Wed Nov 25 10:50:46...

Hi @PrometheusPi I am installing current PIConGPU dev branch with ISAAC 1.5.2 to verify if they work properly from this case. I am having a list of these errors: ```...

I've rechecked dependencies and fixed the Alpaka mismatch issue. With PIConGPU current dev branch and ISAAC 1.5.2 following the next configuration: ``` ################################# ## Section: Required Variables ## ################################# TBG_wallTime="0:30:00"...