3 ms·
Maybe you're right, however OpenCL 2.2 came out 4 years ago and (almost) nobody has adopted it yet, so the problem could be with the spec. OpenCL 3.0 was adopte
by 0-_-0 5y ago
Maybe you're right, however OpenCL 2.2 came out 4 years ago and (almost) nobody has adopted it yet, so the problem could be with the spec. OpenCL 3.0 was adopted by nvidia (although OCL 3.0 is the same as 1.2 with some optional features added)
https://en.wikipedia.org/wiki/OpenCL#OpenCL_2.2_support https://en.wikipedia.org/wiki/OpenCL#OpenCL_2.2_support
- emn13 5y agoBut on that very same wikipedia page you can see it took less than a year for both intel and AMD to release openCL 2.0 drivers, yet nvidia didn't even start evaluating that for years. Then again, it sounds like OpenCL 2.0 required some flexibility the nvidia drivers or hardware wasn't able to provide. It's pretty hard to speculate to which degree nvidia was intentionally sandbagging here, and to which degree it really was stuck. However, it's a member of khronos, and it's hard to believe they as such a major manufacturer could not have either said beforehand that the spec was a problem or simply complied with it; as both AMD and intel did. Also, given CUDA's success it's all rather convenient for nVidia - at the very least it looks like they didn't mind leveraging their market position for continued market dominance, even if it's unclear whether that was an intentionally anti-competitive aim from the get go, or simply a fortunate happenstance they didn't try to avoid. Then again; with antitrust enforcement mostly remaining in vaporware mode it's a little hard to blame them.