This API is so popular and used around the world that its 3.0 specification has had to be upgraded from a multimedia point of view of the devices it hosts.
The first and foremost of the Khronos group had to maintain consistency, something they are sure about on the new level 3.
OpenCL 3.0: a new approach to integration
Due to the number of API types, as in others such as Direct X, the company has confirmed compatibility or backlog compatibility with versions 1.2 with all its applications and OpenCL 2.X versions, in which they developed what they called a unified definition.
In this case, the C ++ language should have been compiled for OpenCL, an open source project supported by Clang. This is fully compliant with CPSC and allows developers to implement multiple C ++ t asks across 17 cores.
The main design comes from two extensions, called Extension Asynchronous Copy and Asynchronous Work Group Copy Fence. Although there is no data that is most appropriate for them at the moment, We know that they allow for a systematic and efficient DMA transaction, which seems to be the best option for Scratch Pad memory, which requires detailed control of the assignments. buffer handler.
Flexibility as the main weapon against its rivals
As we well know, OpenCL has made a huge impact on PC and recent games. Its focus on flexibility allows developers to easily showcase their games across different platforms. Moreover, it is true that being an ever-expanding standard, the Khronos Group never ceases to incorporate functionalities, something very popular with Intel and NVIDIA.
Both companies are excited, because models based on this model allow for the best performance, while on the game developers' side it gives them a huge selection of new generation GPUs such as Xe.
This means that companies like Qualcomm are also getting into operational conflict, as developers are constantly praying for performance and GPU programming language that works across devices, something we have seen with the explosion of the smartphone market. .
The next step seems to be that OpenCL integrates the Vulkan API layers to become the world's most anticipated name for the largest number of devices in history. The only programming language to be able to interact with any CPU or GPU in the world, be it X86 or ARM and even SPIR-V as a back-end.
This should ensure excellent performance and most of all be infected according to the platform, at which time the most notable development of this version of OpenCL 3.0.
