3 ms·
Indeed. Anyone who has worked with ROCm knows that its... well... rough around the edges. But there's something to be said about "documentation is code", I can
by dragontamer 7y ago
Indeed.
Anyone who has worked with ROCm knows that its... well... rough around the edges. But there's something to be said about "documentation is code", I can pull up Clang and straight up see the parser for ROCm -> AMD GPU compiler, as well as pull up the AMD Vega ISA document (https://developer.amd.com/wp-content/resources/Vega_Shader_ISA_28July2017.pdf https://developer.amd.com/wp-content/resources/Vega_Shader_I...) and learn the assembly language.
ROCm is rough around the edges, but it is documented and open source. If all else fails, I can write in assembly and get what I need done.
-------
With that being said, NVidia's CUDA is somewhat open too, since their CUDA -> PTX compiler stuff is also in clang, and PTX is also very well documented.
I guess people are liking AMD's other open-source parts of ROCm. In particular, ROCm getting upstreamed to the Linux kernel proper for better support.
-------
Based on how ROCm has evolved in the past year, they've become more focused. They've cut back on some features (I did like HCC / C++Amp... RIP), and refocused their efforts on what seems to matter.
NVidia CUDA continues to march forward of course, but there's clearly a need for a 2nd player, at very least to compete against the sore-spots of NVidia licensing issues and hardware costs.