You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Supporting more container types would definitely be appreciated. Regarding list and forward_list, getting their design on the GPU right, however, seems not trivial. One idea could be to take inspiration from the internal collision handling of stdgpu::unordered_map (and stdgpu::unordered_set) to implement such a container.
Regarding the HIP backend: Although its design is fairly similar to the CUDA backend, it is still considered experimental due to lack of respective hardware for testing and some rough edges in the ROCm SDK in general. ROCm 6.x also seems to be incompatiable with previous versions, so any contributions in improving the support there are welcome.
Does it make sense to add a list and forward_list container?
What are some ways to optimize this project from the hip direction?
The text was updated successfully, but these errors were encountered: