search for: spirv

Dear all, I have a couple of questions of SPIR-V implementation for OpenCL. The first one is about the tool spirv-opt from the project SPIRV-TOOLS. When you use that tool like "spirv-opt test.spv -o test.spv", it changes something at the file or it does not do anything by not using any flag? I think it is like a "No action" flag but I am not 100% sure about that. The second doubt is about...

...OpenCL in Clang. Several Khronos vendors (ARM, AMD, Intel, Xilinx, Codeplay and others) are interested in adding support for SPIR-V, which should gradually replace the old SPIR once products are no longer shipped with the old format. Here is the detailed description: https://github.com/KhronosGroup/SPIRV-LLVM-Translator/wiki/SPIRV-Toolchain-for-Clang To summarize, the idea is to add a SPIR-V target triple to Clang that can be used to generate a SPIR-V binary for OpenCL code. There was a separate thread regarding generation of SPIR-V binary and the community suggested that a translator from LLVM IR...

On Fri, May 15, 2015 at 11:50 AM, David Chisnall < David.Chisnall at cl.cam.ac.uk> wrote: > On 15 May 2015, at 17:53, Chris Bieneman <beanz at apple.com> wrote: > > > > +1 to lib/Target/SPIRV/(Reader|Writer) > > > > I really like this idea. I’ve talked with some people on both the LLVM > and Khronos sides and I really think adding SPIR-V support to LLVM as an > optional program serialization format would be fantastic. I think it would > make it even easier for LLVM-...

> On May 16, 2015, at 12:21 PM, Liu, Yaxun (Sam) <Yaxun.Liu at amd.com> wrote: > > I am thinking maybe the functionality of the bi-way conversion can be kept at llvm/lib/Bitcode/SPIRV, which will facilitate OpenCL vendors to do conversions between LLVM and SPIR-V. On the other hand, we create a llvm/Target/SPIR-V, which uses llvm/lib/Bitcode/SPIRV to generate SPIR-V. The SPIR-V target allows Clang and other LLVM front ends to target generic OpenCL/Vulkan platforms. I don’t thin...

I note that there was a talk recently at EuroLLVM SPIR-V and LLVM about and so I want to get this message out soon so as to avoid duplicated effort. I have an up to date backend for SPIR-V on an up to date fork (~2-3 weeks behind) of LLVM, transplanted and “modernised” from Khronos’ SPIRV-LLVM that I plan on integrating into LLVM trunk. While it is usable in it’s current form there are several issues. SPIRV-LLVM’s SPIRV support is not a real backend and does not live in /lib/Target/SPIRV. This has been solved, SPIRV is now a proper target(s). I have not copied the tests across yet,...

It is just a header file. All source code is under lib/Target/SPIRV since they really belong there. Those who want to use the conversion functionality just need to link with the SPIRV target library. Any suggestion about a better location for the header file? Thanks. Sam From: Chris Bieneman [mailto:beanz at apple.com] Sent: Wednesday, June 17, 2015 2:31 PM To:...

> This is great to see. Is this code the basis of the forks that Anastasia talked about or did those come from somewhere else? Yes, indeed the base is https://github.com/KhronosGroup/SPIRV-LLVM/ and then there are multiple forks that include some rework as well (some of which were announced on the LLVM channels). I think the biggest problems we are trying to solve is: 1. Keeping up to date with the LLVM code base development. 2. Providing unified common place for everyone to contri...

...e. Cheers, -Neil. On 18/06/15 20:25, Liu, Yaxun (Sam) wrote: > > *From:*Eli Bendersky [mailto:eliben at google.com] > *Sent:* Thursday, June 18, 2015 1:43 PM > *To:* Mehdi Amini > *Cc:* Liu, Yaxun (Sam); llvmdev at cs.uiuc.edu > *Subject:* Re: [LLVMdev] [RFC] Proposal for Adding SPIRV Target > > On Thu, Jun 18, 2015 at 10:26 AM, Mehdi Amini <mehdi.amini at apple.com > <mailto:mehdi.amini at apple.com>> wrote: > > On Jun 18, 2015, at 9:31 AM, Liu, Yaxun (Sam) <Yaxun.Liu at amd.com > <mailto:Yaxun.Liu at amd.com>> wrote: > >...

Hi Chris, The main benefit for LLVM to include SPIRV support directly is to increase the number of users and developers in the area of heterogeneous computing, e.g. GPUs, FPGAs, DSPs. We want to increase the number of such devices that LLVM natively supports by adding compilation to SPIRV due to the shortage of proprietary backends in upstream LLVM...

...u at amd.com> wrote: > > > > *From:* Mehdi Amini [mailto:mehdi.amini at apple.com <mehdi.amini at apple.com>] > > *Sent:* Thursday, June 18, 2015 11:24 AM > *To:* Liu, Yaxun (Sam) > *Cc:* llvmdev at cs.uiuc.edu > *Subject:* Re: [LLVMdev] [RFC] Proposal for Adding SPIRV Target > > > > On Jun 18, 2015, at 6:23 AM, Liu, Yaxun (Sam) <Yaxun.Liu at amd.com> wrote: > > Hi Mehdi, > > Thank you for your comments. My comments are below. > > Sam > > *From:* Mehdi Amini [mailto:mehdi.amini at apple.com <mehdi.amini at apple.com&gt...

On 02/26/2018 09:25 AM, Anastasia Stulova wrote: > >> This is great to see. Is this code the basis of the forks that Anastasia > talked about or did those come from somewhere else? > > > Yes, indeed the base is https://github.com/KhronosGroup/SPIRV-LLVM/ and then there are multiple forks that include some rework as well (some of which were announced on the LLVM channels). I think the biggest problems we are trying to solve is: > > 1. Keeping up to date with the LLVM code base development. > > 2. Providing unified common place fo...

+1 to lib/Target/SPIRV/(Reader|Writer) I really like this idea. I’ve talked with some people on both the LLVM and Khronos sides and I really think adding SPIR-V support to LLVM as an optional program serialization format would be fantastic. I think it would make it even easier for LLVM-based tools to be integrated into...

...to be a part of LLVM for you to do this. You can add > the SPIR-V target to clang and then define a SPIR-V toolchain (i.e. clang/Driver/Toolchains) > that uses the external tool to translate LLVM IR to SPIR-V. Ok. I guess if Clang community accepts this way, it would be better to set up the SPIRV converter as a tool of LLVM. So the question is are there any downsides of this? Or would anyone object if we add the converter to the LLVM project as an optional tool? We would of course take care of configuring and maintaining it ourselves. Cheers, Anastasia ________________________________ Fr...

...he converter as part of LLVM can help expand LLVM's >>> value proposition in heterogeneous computing, in part by complementing >>> the OpenCL C backend in clang. >>> >>> Thus I would like to ask what the LLVM community needs to see from us >>> before SPIRV-LLVM can be accepted as an external tool, if at all. >>> >> >> Does the external tool exist already? I recommend starting by posting >> the code publicly and then ensuring that going forward all development >> and discussions about the tool are happening in a publi...

...u can add >>> the SPIR-V target to clang and then define a SPIR-V toolchain (i.e. clang/Driver/Toolchains) >>> that uses the external tool to translate LLVM IR to SPIR-V. >> >> >> Ok. I guess if Clang community accepts this way, it would be better to set up the SPIRV converter as a tool of LLVM. >> >> So the question is are there any downsides of this? Or would anyone object if we add the converter to the LLVM project as an optional tool? We would of course take care of configuring and maintaining it ourselves. > > There is no requirement th...

...gt; Could you please link the thread mentioned? > > Thanks, > Nic > > P.S. Feel free to use the tablegen descriptions of the SPIR-V format from > [2] > > [1]: http://lists.llvm.org/pipermail/llvm-dev/2017-May/112538.html > [2]: https://github.com/thewilsonator/llvm-target-spirv > > On 10 Sep 2018, at 11:10 pm, Anastasia Stulova via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > Hello, > > Since 2015 Khronos has switched to the new portable intermediate format > SPIR-V, which has replaced the original SPIR. The advantage is that it > o...

...you to do this. You can add >> the SPIR-V target to clang and then define a SPIR-V toolchain (i.e. clang/Driver/Toolchains) >> that uses the external tool to translate LLVM IR to SPIR-V. > > > Ok. I guess if Clang community accepts this way, it would be better to set up the SPIRV converter as a tool of LLVM. > > So the question is are there any downsides of this? Or would anyone object if we add the converter to the LLVM project as an optional tool? We would of course take care of configuring and maintaining it ourselves. There is no requirement that the tool needs...

...that having the converter as part of LLVM can help expand LLVM's > > value proposition in heterogeneous computing, in part by complementing > > the OpenCL C backend in clang. > > > > Thus I would like to ask what the LLVM community needs to see from us > > before SPIRV-LLVM can be accepted as an external tool, if at all. > > > > Does the external tool exist already? I recommend starting by posting > the code publicly and then ensuring that going forward all development > and discussions about the tool are happening in a public space. The cod...

Here is the revised proposal for the LLVM/SPIR-V converter. Please comment. Thanks. Proposal of Adding SPIRV Target Background SPIR-V is a portable binary format for OpenCL kernels and GLSL shaders. A typical use case of SPIR-V is as follows: 1. An application developer uses Clang to compile an OpenCL kernel source code to a SPIR-V binary which is common for all OpenCL platforms. 2. The app...

...25, Liu, Yaxun (Sam) wrote: >>> *From:*Eli Bendersky [mailto:eliben at google.com] >>> *Sent:* Thursday, June 18, 2015 1:43 PM >>> *To:* Mehdi Amini >>> *Cc:* Liu, Yaxun (Sam); llvmdev at cs.uiuc.edu >>> *Subject:* Re: [LLVMdev] [RFC] Proposal for Adding SPIRV Target >>> >>> On Thu, Jun 18, 2015 at 10:26 AM, Mehdi Amini <mehdi.amini at apple.com >>> <mailto:mehdi.amini at apple.com>> wrote: >>> >>> On Jun 18, 2015, at 9:31 AM, Liu, Yaxun (Sam) <Yaxun.Liu at amd.com >>> <mai...