pika
pika copied to clipboard
pika-org
pika builds on C++ std::execution with fiber, CUDA, HIP, and MPI support.
Assuming we don't require our own version for e.g. CUDA and the replacements actually work, we need to take care that the following don't get worse: - compile time -...
Currently, if the queue of pending threads is empty on a worker thread, `get_next_thread` returns, the scheduler goes to add new threads from the staged to pending threads, and then...
The sender/receiver CPOs currently use a helper base class to define fallback implementations with `tag_fallback_invoke`. The need for `tag_fallback_invoke` should be revisited and the CPO types should potentially be in...
The event polling has been successful and turned out to perform significantly better than using CUDA callbacks. However, that was tested when the CUDA callbacks still required runtime registration on...
Investigate seg faults from the tests that have been excluded from the MacOS Arm64 workflow in #469. Listed here: https://github.com/pika-org/pika/blob/89fdaa20caa3f95c59dbe02cbdd0a287c3d21acc/.github/workflows/macos_arm64_debug.yml#L64-L70.
I have no idea what could be causing this.
`hello_world` build unit test hangs with clang + cuda when pika is configured in debug mode and the `hello_world` project in debug mode.
To `runtime_state`? And possibly at the same time use a separate enum for the scheduler state.
This is required to unconditionally use the P2300 reference implementation. nvcc/nvc++ is currently the only compiler holding us back.