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
I am wondering what the scope of this is. We are maintaining and working on various standard library pieces (https://github.com/kokkos/mdspan, https://github.com/kokkos/stdblas). However, one of our requirements is back porting to C++17 standards which are actually currently used in HPC (right now 17 as the base, but starting to switch to 20) and another is to support GPUs, i.e. we need device markup, we need to work around a bunch of std:: features (e.g. array, pair, etc.) not fully working in CUDA/HIP code etc.. Is this in scope or out of scope? Do you only want features accepted in the draft, or also proposed?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am wondering what the scope of this is. We are maintaining and working on various standard library pieces (https://github.com/kokkos/mdspan, https://github.com/kokkos/stdblas). However, one of our requirements is back porting to C++17 standards which are actually currently used in HPC (right now 17 as the base, but starting to switch to 20) and another is to support GPUs, i.e. we need device markup, we need to work around a bunch of std:: features (e.g. array, pair, etc.) not fully working in CUDA/HIP code etc.. Is this in scope or out of scope? Do you only want features accepted in the draft, or also proposed?
Beta Was this translation helpful? Give feedback.
All reactions