7 ms·
better yet, use SPIR and OpenCL. HSA is polluting the GPGPU space, along with CUDA. we need less proprietary crap, and more open standards.
by foxhill 13y ago
better yet, use SPIR and OpenCL.
HSA is polluting the GPGPU space, along with CUDA. we need less proprietary crap, and more open standards.
- pjmlp 13y agoHSA is a standard like many other in the industry. OpenCL cannot offer what CUDA does in terms of tooling.
- foxhill 13y agothere are far fewer vendors behind HSA than SPIR. AMD and ARM seem to be pushing it hard (and argue it compliments rather than competes with SPIR). but it's just muddying the waters. hmm, you'll need to be specific about what OpenCL lacks, as there are a lot of tools out there (and a lot of them support CUDA as well)
- pjmlp 13y ago> there are far fewer vendors behind HSA than SPIR. AMD and ARM seem to be pushing it hard (and argue it compliments rather than competes with SPIR). but it's just muddying the waters. It will also be the official GPGPU for Java. > hmm, you'll need to be specific about what OpenCL lacks, as there are a lot of tools out there (and a lot of them support CUDA as well) Ability to write kernels in C++, Fortran or any other language that targets PTX.
- salient 13y agoWhat's not open about HSA? If Intel and Nvidia haven't joined it (yet) doesn't mean it's not open. Nvidia treats OpenCL as 2nd class citizen compared to CUDA anyway, and I don't think Intel is that interested in OpenCL anymore, now that they have Phi. So if neither party is too interested in OpenCL, then I'd rather have HSA than the actual proprietary CUDA/Phi solutions.
- foxhill 13y agothere are fewer vendors behind it. nvidia certainly do treat OpenCL as a second class citizen, and it's incredibly frustrating. however, Intel are very interested in OpenCL, it's their preferred programming model for the Phi..