3 ms·
The elephant in the room is that language development seems basically stalled. Meanwhile the bad old "C for GPUs" languages we are stuck with are CUDA, Metal an
by fulafel 11y ago
The elephant in the room is that language development seems basically stalled. Meanwhile the bad old "C for GPUs" languages we are stuck with are CUDA, Metal and OpenCL, of which OpenCL is no good wrt compiler/tools/driver quality and the other two are proprietary and thus of limited potential.
- exDM69 11y agoWell everything is about to change once we get the SPIR-V intermediate language for Vulkan (and possibly OpenGL and CL too). It's an intermediate language with some similarity to LLVM IR. That should enable 3rd parties to author compilers targetting SPIR-V, allowing other programming languages without having to use C as an intermediate target.
- markus2012 11y agoWhat bout HSAIL / LLVM: https://github.com/HSAFoundation/HLC-HSAIL-Development-LLVM https://github.com/HSAFoundation/HLC-HSAIL-Development-LLVM (HSA Intermediate Language LLVM support) It would seem an IR is already available and it's already integrated on an existing LLVM branch. From skimming around it seems AMD has been working hard to do what is necessary to get things merged into LLVM mainline. <quote> My highest priority is to get the backend upstreamed as soon as possible, so I would appreciate feedback about any kinds of blocking issues on that. Thanks Matt Arsenault </quote> http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-May/085545.html http://lists.cs.uiuc.edu/pipermail/llvmdev/2015-May/085545.h...
- exDM69 11y agoI'm sure this work hasn't gone unnoticed in SPIR-V development, I wouldn't even be surprised if it's partially the same guys doing it. That said, I haven't been involved in that so I don't know for sure. LLVM IR has a few weak points for this kind of IR. It has architecture dependent parts and the format has changed in the past so it is coupled to LLVM development cycles. You can argue whether that's a good or bad thing but it's a thing to be considered. There were two earlier versions of SPIR, coupled with different LLVM versions. SPIR-V is independent of LLVM but still semantically similar to LLVM IR, so compiling back and forth between the two isn't too difficult. AFAIK there has been discussions about adding a SPIR-V backend to LLVM trunk (can't find the mailing lists). The SPIR-V spec is already out and there has been some projects already using it, although you can't run it on a GPU yet (unless you work for a GPU vendor, that is). https://www.khronos.org/spir https://www.khronos.org/spir
- fulafel 11y agoThere's some hope on the medium term from SPIR-V but there are a lot of risks for getting this in near future. To make for an inviting GPGPU code generation in target in near future, they have to nail all of a) good platform coverage in quick schedule, b) uniformly good enough implementation quality and reliability for large non-graphics codes and c) sufficient feature set uniformity for portable code generation. And even then it will take years for languages to appear, win in userbase over competitors, and mature.
- sklogic 11y agoLanguage development have not been "stalled", it's just mainly under the radar. Some nice designs are out there, see Vobla and Pencil [1] for example, or Harlan [2] as another extreme. [1] http://carp.doc.ic.ac.uk/external/dissemination.php http://carp.doc.ic.ac.uk/external/dissemination.php [2] http://blog.theincredibleholk.org/blog/2013/06/28/announcing-the-release-of-harlan/ http://blog.theincredibleholk.org/blog/2013/06/28/announcing...
- fulafel 11y agoI agree there's some activity, but "stalled" is even understating it in my view. The current activity level is much lower compared to some time back when GPGPU programming seemed to be enjoying relatively wide industry backing. But to take these two, they clearly look like academic proof-of-concept software and not something headed for widespread production use any time soon.
- sklogic 11y agoCARP project is well funded by the EU and aims at the low power supercomputing applications (see the Mont-Blanc project [1]), so it's not that far from practical applications. [1] https://www.montblanc-project.eu/ https://www.montblanc-project.eu/
- ybacon 11y agoI agree, but in HPC, the primary consumer of GPGPU so far, there is a lot of knowledge locked into C/C++/Fortran codebases and porting to a new language is a huge commitment with an uncertain reward. I think this is a big problem with language design for heterogeneous computing. I've been following the development of OpenACC, which is has been gaining momentum and lets you write GPU code directly with C with pragmas (like OpenMP). It's a bit more performance portable between platforms than CUDA or OpenCL with a low initial investment. I'm a little concerned about the lack of diversity of compilers supporting it, but it seems like the most feasible route to move those big codebases to heterogeneous platforms. [1] http://www.openacc.org/ http://www.openacc.org/