When Khronos realised they should have had their own PTX (SPIR) and higher level programming models, the race was already lost.
When Khronos realised they should have had their own PTX (SPIR) and higher level programming models, the race was already lost.
OpenCL advertised "write once, run everywhere" approach, it was completely bonkers when it comes to HPC. Optimizations that one applies on different hardware make code look completely different. It has its niche, but not in HPC. I am no longer in this industry, so maybe things changed. But at the time, some teams picked up OpenCL and quickly dropped, as it didn't give enough bang for a buck, and tooling didn't compare with rather polished CUDA stuff.
"Optimizations that one applies on different hardware make code look completely different."
Unless you got C program where this statement is true.
I'm still having hard time to believe that kernels optimized for SIMD architecture will be useful on CPU and vice versa. And OpenCL people advertised this, if memory serves me well.
https://arcb.csc.ncsu.edu/~mueller/cluster/nvidia/2.0/Progra...
When did C started supporting templates?
And that's what their docs say too.
C++ class was added in 2010 as answered in another thread, in CUDA 3.0.
I thought you were pretty sure about CUDA 5.0.
Which is easily proven when reading the documentation for the first set of CUDA releases.
As for the rebooted hardware design,
https://developer.nvidia.com/cuda-toolkit-21-january-2009
> C++ templates are now supported in CUDA kernels
Or maybe 2010 with CUDA 3.0, to make up for your C++ classes.
https://developer.nvidia.com/cuda-toolkit-30-downloads
> C++ Class Inheritance and Template Inheritance support for increased programmer productivity
Let me check the date, I think we are in 2020, so if my math doesn't betray me, it looks like about 10 years to me.
From where I am standing, I am pretty sure you never used CUDA.