Yeah, really tiny... At first I thought 'wow this is a game changer', but then I looked at your link and thought 'what's the point?'. Can someone explain what real problems you can solve with just the headers in the link above?
I guess that the point is that when writing CUDA code (which looks like C++), you can use these libraries which are homogenous with CPU code.
Looking at the functions, chrono/barrier etc require CPU level abstractions, so using the STL versions (which are for the CPU) aren't going to work really.
I would have expected the <algorithm> header, but instead...synchronization primitives? std::chrono? I'm completely baffled about how that would be useful, but that's probably because I know very little about CUDA.
shaklee3|5 years ago
blelbach|5 years ago
roel_v|5 years ago
jpz|5 years ago
Looking at the functions, chrono/barrier etc require CPU level abstractions, so using the STL versions (which are for the CPU) aren't going to work really.
happyweasel|5 years ago
blelbach|5 years ago
https://youtu.be/VogqOscJYvk
TillE|5 years ago
blelbach|5 years ago
Our end goal is to enable the full C++ Standard Library. The current feature set is just a pit stop on the way there.