search for: khronosgroup

...eed to do something like: > > clang -std=c99 add_numbers.c -lOpenCL -I/path/to/folder/with/CL/cl.h > > > > Usually, libOpenCL.so and CL/cl.h are provided by OpenCL SDKs from HW/SW > vendor, for example: [1], [2], [3], [4] and others [5] > > But, you can also get them from KhronosGroup repos: OpenCL-ICD-Loader [6], > OpenCL-Headers [7] > > > > > I want to do that the .c file uses the .cl that i have compiled before > with clang and i do not know how to do it. > > > > This is an interesting question. Basically, in OpenCL you can build your > dev...

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:

...to [2]. > > > > Is there an option for clang or an LLVM clang to do the mangling for spir > builtins? > > > > Thanks > > Hongbin > > > > > > [1] https://www.khronos.org/registry/spir/specs/spir_spec-2.0.pdf, page 36 > > [2] https://github.com/KhronosGroup/SPIR-Tools/wiki/ > SPIR-2.0-built-in-functions > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160912/1550f861/attachment.html>

...R format for 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 L...

...s ([6 x i8], [6 x i8] addrspace(2)* @.str, i64 0, i64 0)) with the following command line: clang -cc1 -internal-isystem /wrk/xsjhdnobkup2/hongbinz/omp/build-llvm/bin/../lib/clang/3.9.0/include -nostdsysteminc -S -emit-llvm -o - Is this the correct behavior? Thanks Hongbin [1] https://github.com/KhronosGroup/SPIR-Tools/wiki/SPIR-2.0-built-in-functions [2] http://clang.llvm.org/doxygen/opencl-c_8h_source.html On Mon, Sep 12, 2016 at 1:43 PM, Hongbin Zheng <etherzhhb at gmail.com<mailto:etherzhhb at gmail.com>> wrote: Thanks a lot. On Mon, Sep 12, 2016 at 1:42 PM, Liu, Yaxun (Sam) <Yaxun...

I am already successfully generating SPIR-V with a forward port of Khronos’ SPIR-V LLVM. What does one need in order to generate SPIR? From what I gather it is based on a specific LLVM IR version (3.4?) with a bunch of metadata. Is it possible to generate SPIR from LLVM trunk? If so how? Thanks Nic -------------- next part -------------- An HTML attachment was scrubbed... URL:

...7 ret void } In this case, get_global_id is not mangled to _Z13get_global_idj according to [2]. Is there an option for clang or an LLVM clang to do the mangling for spir builtins? Thanks Hongbin [1] https://www.khronos.org/registry/spir/specs/spir_spec-2.0.pdf, page 36 [2] https://github.com/KhronosGroup/SPIR-Tools/wiki/SPIR-2.0-built-in-functions -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160912/2507fc3e/attachment.html>

...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 >...

> 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...

...ral 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 com...

...s ([6 x i8], [6 x i8] addrspace(2)* @.str, i64 0, i64 0)) with the following command line: clang -cc1 -internal-isystem /wrk/xsjhdnobkup2/hongbinz/omp/build-llvm/bin/../lib/clang/3.9.0/include -nostdsysteminc -S -emit-llvm -o - Is this the correct behavior? Thanks Hongbin [1] https://github.com/KhronosGroup/SPIR-Tools/wiki/SPIR-2.0-built-in-functions [2] http://clang.llvm.org/doxygen/opencl-c_8h_source.html On Mon, Sep 12, 2016 at 1:43 PM, Hongbin Zheng <etherzhhb at gmail.com<mailto:etherzhhb at gmail.com>> wrote: Thanks a lot. On Mon, Sep 12, 2016 at 1:42 PM, Liu, Yaxun (Sam) <Yaxun...

...nCL 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 sugge...

...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 code is publicly available at https://github.com/pierremoreau/llvm-spirv. It is based on https://github.com/KhronosGroup/SPIRV-LLVM/ and https://github.com/thewilsonator/llvm-target-spirv/, stripped 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...

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 pl...

...tarting 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 code is publicly available at https://github.com/pierremoreau/llvm-spirv. > It is based on https://github.com/KhronosGroup/SPIRV-LLVM/ and > https://github.com/thewilsonator/llvm-target-spirv/, stripped 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.) This is great to...

...f the length allocated and can fill that in if size is zero. However, requiring all allocations to be made with clSVMAlloc() defeats the goal of being able to use regular malloc() and mmap() allocations for OpenCL implementations that support fine-grained system allocations. (See https://github.com/KhronosGroup/OpenCL-Docs/issues/392) So if the size isn't specified, the most logical choices are do nothing and return OK, return an error, or assume that at least one byte is being migrated and try migrate it.

...nos 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 bin...

...<dnovillo at google.com> Subject: Re: US LLVM Dev Meeting 2019 - Round Table - Challenges using LLVM for GPU compilation Dear all, Could I suggest adding one more topic to the list related to GPUs? We have just published a prototype for a LLVM backend generating SPIR-V at https://github.com/KhronosGroup/LLVM-SPIRV-Backend. While I won't be present at the round table, inputs from the LLVM community on how to upstream this backend to LLVM would be greatly appreciated. Thank you. Kind regards, Marco ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on...

...Re: [llvm-dev] SPIRV-LLVM as an external tool 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 plac...

...nal tool > > 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 u...