| 23 Sep 2025 |
 Hugo | Is that a known bug in Nix or in the build tools? | 10:22:55 |
|  kenji changed their display name from a-kenji to kenji. | 10:42:31 |
 Albert Larsan | nvcc spawns multiple compiler instances per invocation, and ninja spawns as many nvcc instances as the number of cores/threads, which makes the CPU overcommited (ex: you have 16 threads, ninja spawn 16 nvcc instances, and each one of the nvcc intances spawns 6 cicc instances, and each cicc instance consumes one full cpu thread. So you end up with 16*6=96 processes trying to run at the same time). The build is not stuck, it just takes a very long time to happen (because it tries to do more at the same time than your computer can handle) | 11:32:01 |
| Hugo | Tanks for this explanation. My impression is more that the system goes OOM and then something gets stuck and never resumes. | 11:44:59 |
| Hugo | Especially since a working build (previous release) finished in 14 minutes. | 12:08:09 |
 Gregor Burger | Hi Guys, quick question is there an equivalent cudaPackages.backendStdenv for clang? | 12:09:25 |
