search for: clcreateprogramwithil

...ipped off of everything not related to SPIR-V and updated to work with llvm HEAD. (Some of the commits were lost on the way, so we are in the process of redoing the stripping and updating.) One user of that external tool will be Mesa [1] (for its OpenCL implementation named clover) for 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by translating SPIR-V to LLVM IR; (patches under review [2]) 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating from SPIR-V to NIR). Regards, Pierre...

...g > the stripping and updating.) This is great to see. Is this code the basis of the forks that Anastasia talked about or did those come from somewhere else? -Tom > > One user of that external tool will be Mesa [1] (for its OpenCL implementation > named clover) for > 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by > translating SPIR-V to LLVM IR; (patches under review [2]) > 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by > clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating > from SPIR-V to NIR...

...ng > the stripping and updating.) This is great to see. Is this code the basis of the forks that Anastasia talked about or did those come from somewhere else? -Tom > > One user of that external tool will be Mesa [1] (for its OpenCL implementation > named clover) for > 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by > translating SPIR-V to LLVM IR; (patches under review [2]) > 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by > clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating > from SPIR-V to NIR...

...ipped off of everything not related to SPIR-V and updated to work with llvm HEAD. (Some of the commits were lost on the way, so we are in the process of redoing the stripping and updating.) One user of that external tool will be Mesa [1] (for its OpenCL implementation named clover) for 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by translating SPIR-V to LLVM IR; (patches under review [2]) 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating from SPIR-V to NIR). Regards, Pierre...

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:

...This is great to see. Is this code the basis of the forks that Anastasia > talked about or did those come from somewhere else? > > -Tom > >> >> One user of that external tool will be Mesa [1] (for its OpenCL implementation >> named clover) for >> 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by >> translating SPIR-V to LLVM IR; (patches under review [2]) >> 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by >> clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating >> fr...

On 02/21/2018 12:15 AM, Tomeu Vizoso via llvm-dev wrote: > Hi, > > for a few months already I have been asking around for opinions on how > people could best work together on Khronos' SPIR-V <-> LLVM-IR converter > and some consensus seems to have formed. > > Most of the people I talked to favored having the converter become an > external tool within the LLVM

...gt; This is great to see. Is this code the basis of the forks that Anastasia > talked about or did those come from somewhere else? > > -Tom > >> >> One user of that external tool will be Mesa [1] (for its OpenCL implementation >> named clover) for >> 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by >> translating SPIR-V to LLVM IR; (patches under review [2]) >> 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by >> clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating >> fr...

...OpenCL spec doesn’t define binary format, > i.e. it is implementation-defined. Usually each vendor provides so-called > “offline compiler” tool which allows you to get device binary for your > OpenCL code – the binary is not portable across different devices/vendors > 3. Use clCreateProgramWithIL + clBuildProgram: requires OpenCL 2.1 or > cl_khr_il_program extension. Allows you to create program from SPIR-V. > Basically, this is kind of combination of online and offline models: one > the one side, you need to launch offline compiler to parse source code and > get SPI...

...code the basis of the forks that Anastasia >> talked about or did those come from somewhere else? >> >> -Tom >> >>> >>> One user of that external tool will be Mesa [1] (for its OpenCL implementation >>> named clover) for >>> 1. enabling clCreateProgramWithIL(KHR)? on AMD cards through clover, by >>> translating SPIR-V to LLVM IR; (patches under review [2]) >>> 2. allowing additional drivers (nouveau, freedreno, etnativ) to be supported by >>> clover, by compiling OpenCL C (via LLVM IR) to SPIR-V (and then translating &g...

Hi, for a few months already I have been asking around for opinions on how people could best work together on Khronos' SPIR-V <-> LLVM-IR converter and some consensus seems to have formed. Most of the people I talked to favored having the converter become an external tool within the LLVM project, similar to libclc. I think that the LLVM project's processes, infrastructure and