search for: clspv

...uate inclusion in LLVM proper once things are more mature. One path for me would be to take Khronos' or Nic's work and convert it into something that can be packaged by Linux distributions (so it needs to work with the latest LLVM release, with no patches). Another path would be to extend clspv to cover the whole of OpenCL, but I don't know if Codeplay/Google are interested in taking such patches. Is here interest in coordinating efforts? Regards, Tomeu

...things are > more mature. > > One path for me would be to take Khronos' or Nic's work and convert it > into something that can be packaged by Linux distributions (so it needs > to work with the latest LLVM release, with no patches). > > Another path would be to extend clspv to cover the whole of OpenCL, but > I don't know if Codeplay/Google are interested in taking such patches. > > Is here interest in coordinating efforts? > I recommend using clspv, in addition to having a clang-based driver for compiling OpenCL C, it exposes the LLVM IR -> SPIR...

...to the build system to make it work with 5.0. The code generator is a regular (well for the purposes of a front end developer) backend so should be very easy to integrate. It does lack an OpenCL C front end though, you would need to forward port Khronos’ one. > Another path would be to extend clspv to cover the whole of OpenCL, but > I don't know if Codeplay/Google are interested in taking such patches. > > Is here interest in coordinating efforts? > > Regards, > > Tomeu Definitely although I’m a bit busy at the moment. I hope you can make it to IWOCL. Nic

...arts of the spec. > The vulkan GLSL extended instructions are here - https://www.khronos.org/registry/spir-v/specs/1.0/GLSL.std.450.html Thanks, they look much less convoluted than OpenCL’s. > An example of where we'd need significant changes to support Vulkan https://github.com/google/clspv/blob/master/lib/ReplacePointerBitcastPass.cpp (Vulkan SPIR-V does not allow pointer bitcasts at all - we needed to transform any code that used this pattern into a load as the original type and then bitcast the value instead). I am not a backend person - it'd be useful to me if anyone who is a...

...e folk at KhronosGroup and consolidate the work done for inclusion into LLVM. Nic > On 17 Jul 2017, at 9:55 pm, Neil Henning via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hey all, > > Code finally got through legal, but the repo is live here https://github.com/google/clspv > > This codebase is somewhere between alpha/beta as an estimate, but we've pushed a 1 million line OpenCL C codebase through it and got fully formed Vulkan SPIR-V out the other end. > > I did not want to make the mistake of forking LLVM/Clang - so there are a bunch of passes in t...

On 06/21/2017 09:18 AM, Neil Hickey wrote: > Hi Tom, > > I don't disagree, on a technical level, with any of your points. This is, as you have already pointed out, not the first time we have had this discussion and so far, two years after these discussions were first opened we are not any nearer to a solution that makes sense for all stake holders, hence why I think it prudent to

Hello, I'm trying to build an application and would like to load SPIR-V binary files, and JIT Compile it via LLVM to run shaders on CPU. I would like to use a library (or possibly build my own) that parses SPIR-V and JIT compiles via LLVM API. Then the library can provide C++ interface to compiled data in memory, and I can access resources or call shader methods via the interface. The