Good videos, with context.
The One-Decade Task: Putting std::atomic in CUDA. - Olivier Giroux - CppCon 2019

The One-Decade Task: Putting std::atomic in CUDA. - Olivier Giroux - CppCon 2019

CppCon
0 HN recommenders · discussed 2019–2022
Open YouTube ↗

About this video

Olivier Giroux's CppCon 2019 talk recounts the roughly ten-year effort to bring std::atomic and the C++ memory model to CUDA GPUs, through ten stories from that work.

Why it appears in the archive

Cited as a reference when discussing NVIDIA's C++ memory model, libcu++, and GPU C++ resources.

AI-generated summary and labels from the source dataset; verify important details against the video. Source & credits.

From the Hacker News discussion

pjmlp · 2019-12 · reference

Right now, NVidia is designing their GPGPUs to run C++ code. [LINK] [VIDEO] With Intel just releasing oneAPI (aka Data Parallel C++) last month, and Khronos pushing SYCL as alternative to CUDA C++. It took 30 years for C++ to reach this stage, and in some domains (like embedded) it is still fighting for relevance. That is something to keep in mind whenever to advocate Rust as replacement for Domain XYZ.

Read original comment ↗
davvid · 2020-09 · reference

Here's a somewhat related talk from CppCon '19: "The One-Decade Task: Putting std::atomic in CUDA" [VIDEO]

Read original comment ↗
pjmlp · 2021-04 · reference

CppCon 2019: Olivier Giroux “The One-Decade Task: Putting std::atomic in CUDA.” [VIDEO] Future of ISO and CUDA C++ [LINK] Thrust, the CUDA C++ template library [LINK] Optix, single-ray shader programming model using C++, and ray Tracing acceleration using RT Cores. [LINK] Phew, so many wrappers yet to list.

Read original comment ↗
pjmlp · 2021-08 · reference

Sure, "CppCon 2016: “Bringing Clang and C++ to GPUs: An Open-Source, CUDA-Compatible GPU C++ Compiler" [LINK] "CppCon 2019: Olivier Giroux “The One-Decade Task: Putting std::atomic in CUDA.”" [VIDEO] "Octane render. The Future of GPU Rendering: Real-Time Raytracing" (with CUDA) [LINK] NVIDIA HPC SDK [LINK]

Read original comment ↗
moonchild · 2022-10 · reference

> I really wish that everybody would finally admit that the "fixed function pipeline" is dead There is a great deal of space between 'fixed function pipeline' (which no one is using) and 'all compute all the time' (which pretty much no one is using for real-time graphics either). > GPUs don't yet have a well-defined memory model Nvidia has a memory model. (I have heard--from an nvidia employee--that amd plays a bit more fast and loose.) [VIDEO] > GPUs don't have the equivalent of an MMU--so they can't be partitioned or protected. etc. You do not need an MMU to partition or to protect. (Not to say that GPU security isn't a shitshow.) > The problem is that switching to a "compute" model and making that work well would commodify the GPU--and that's the last thing that AMD and NVIDIA want. [LINK] look at where nvidia's revenue is coming from, and tell me again that they're not already there.

Read original comment ↗