[llvm-dev] SPIRV-LLVM as an external tool

Anastasia Stulova via llvm-dev
Thu, 22 Feb 2018 18:38:13 -0000

> It's important to demonstrate that there is a developer community
backing
> the tool and that it won't be abandoned if it is added as an llvm
> sub-project.
>
> -Tom


Just to complete the picture, this is an initiative from within Khronos Group

to unify our effort to make this available as an LLVM component. A number of

companies have been involved in the original development of this converter and

there are more that have adopted this design in their propriety or open source

toolchains. Mesa and AMD Vulkan driver
(https://github.com/GPUOpen-Drivers/AMDVLK)

are just some examples of the open source ones. There were a number of threads

regarding putting this work upstream in the past years. And due to several

conceptual differences it, unfortunately, took us a while to get an agreement

on the best integration approach. During this time a number of forks were
created

that rebased this work to the top of trunk and also committed several
improvements.

Some of them are just duplicated in various forks. It would help us if we
finally

have it integrated with LLVM so we can keep it up to date and contribute common

changes. So there are a number of companies that want to contribute to this

currently.


@Tom, if you have any valuable experience to share with us on how to get this

accepted/integrated as a tool, it would be very helpful.

Thanks,
Anastasia

________________________________
From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Pierre
Moreau via llvm-dev <llvm-dev at lists.llvm.org>
Sent: 21 February 2018 23:34
To: tstellar at redhat.com
Cc: LLVM Developers; Tomeu Vizoso
Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool

On 2018-02-21 — 14:55, Tom Stellard via llvm-dev wrote:
> 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 project, similar to libclc. I think that
> > the LLVM project's processes, infrastructure and community form
the best
> > place for this collaboration to happen.
> >
> > I hope 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 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 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

[1]: https://www.mesa3d.org/
[2]: https://patchwork.freedesktop.org/series/38728/

> It's important to demonstrate that there is a developer community
backing
> the tool and that it won't be abandoned if it is added as an llvm
> sub-project.
>
> -Tom
>
> > Thanks,
> >
> > Tomeu
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20180222/f7992304/attachment.html>