search for: iwocl

...Moving forward, other than securing the triples spirv32, spirv64, and spirvlogical from LLVM, how can we go about coordinating efforts? I feel that having one backend is a better use of everybody’s time than having three. If we don't get around to anything I’m sure we can organise something at IWOCL. Hi there, any news on coordination? We have customers who are successfully using Mesa in their products, and that are now asking about OpenCL. My current impression is that easiest would be to do what Tom suggested before, and only re-evaluate inclusion in LLVM proper once things are more matur...

> On 27 Sep 2017, at 8:21 pm, Tomeu Vizoso <tomeu.vizoso at collabora.com> wrote: > > Hi there, > > any news on coordination? We have customers who are successfully using > Mesa in their products, and that are now asking about OpenCL. None yet, I’m still waiting for IWOCL to spearhead the coordination. > My current impression is that easiest would be to do what Tom suggested > before, and only re-evaluate 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 > in...

...Moving forward, other than securing the triples spirv32, spirv64, and spirvlogical from LLVM, how can we go about coordinating efforts? I feel that having one backend is a better use of everybody’s time than having three. If we don't get around to anything I’m sure we can organise something at IWOCL. > > Hi there, > > any news on coordination? We have customers who are successfully using > Mesa in their products, and that are now asking about OpenCL. > What hardware are they using? Note that SPIR-V is not required to run mesa's OpenCL on AMD hardware. > My curren...

...Moving forward, other than securing the triples spirv32, spirv64, and spirvlogical from LLVM, how can we go about coordinating efforts? I feel that having one backend is a better use of everybody’s time than having three. If we don't get around to anything I’m sure we can organise something at IWOCL. Nic (Sorry forgot to hit reply all last time)

Dear all, After a huge amount of time trying to install LLVM and Clang i could finally do it, so now im trying to use this tools for generating a bytecode, then apply it modular optimizations and then generate an executable to test the result. First, I only want to compile a project and execute it to see how it works, specifically this one:

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

...> > > > > [1]: https://software.intel.com/en-us/opencl-sdk > > [2]: https://developer.nvidia.com/opencl > > [3]: https://github.com/GPUOpen-LibrariesAndSDKs/OCL-SDK/releases > > [4]: https://developer.arm.com/solutions/graphics/apis/opencl > > [5]: https://www.iwocl.org/resources/opencl-implementations/ > > > > [6]: https://github.com/KhronosGroup/OpenCL-ICD-Loader > > [7]: https://github.com/KhronosGroup/OpenCL-Headers > > > > > > *From:* llvm-dev <llvm-dev-bounces at lists.llvm.org> *On Behalf Of *Enrique > Gonzal...

Yet another implementation of the backend, heh. I’d just started in earnest writing a tablegen based one, with the main goal of fixing the intrinsics to actually be intrinsics. I think it would be a good idea to join forces with the 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