search for: thewilsonator

...Sparc and RISCV. Due to the lack of a Dyld and the fact that SPIR-V is intermediate format, there is no point of a jit, Simple optimisations (CSE,DCE, some very simple inlining) would be nice to have, as would DebugInfo support. The code is available at my GitHub: SPIRV backend https://github.com/thewilsonator/llvm-target-spirv LLVM https://github.com/thewilsonator/llvm/tree/compute should you want to inspect/offer advice. I am very busy until about July, but I just want to put this out here to gather interest / feedback / contributors. Thanks, Nicholas Wilson -------------- next part -------------- An...

...he 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 be Mesa [1] (for its OpenCL implementation named...

...n 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 see. Is this code the basis of the forks that Anasta...

...ny other LLVM backend? > 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...

...en 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 see. Is this code the basis of the forks that Anasta...

...he 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 be Mesa [1] (for its OpenCL implementation named...

...ad 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 <mailto:llvm-dev at lists.llvm.org>> wrote: > >> > >> Hello, > >> > >> Since 2015 Khronos has switched...

...e 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 <mailto:llvm-dev at lists.llvm.org>> wrote: >>> >>> Hello, >>> >>> Since 2015 Khronos has switched to the new...

...g 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 see. Is this code the basis of...

..., > >>> 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 <mailto:llvm-dev at lists.llvm.org>> wrote: > >>>> > >>>> Hello, > >>>> > >&gt...

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

...ng 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 see. Is this code the basis of...

...pment >>>> 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 see. Is th...

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 offers higher portability across different toolchains. There was a talk about it at a Dev Meeting: http://llvm.org/devmtg/2017-03//2017/02/20/accepted-sessions.html#17 LLVM currently only supports SPIR format for OpenCL in Clang. Several Khronos

> On 2 May 2017, at 8:48 am, Tom Stellard <tstellar at redhat.com> wrote: > You would probably need to write a new tablegen backend to generate > instruction tables that would be used outside of LLVM. I think I need to write one anyway because I need to generate lots of tables other than the instruction table (there are no registers and therefore no register table), at least one

On 06/20/2017 05:41 PM, Neil Hickey wrote: > Hi all, I'd like to kick this discussion off again, and summarise the points that have been expressed so far. > > Firstly, as a member of Khronos, I'd like to state that this would be a very interesting development. > Hi Neil, I am very interested in having a good LLVM IR -> SPIR-V solution, and I think it's great that

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