search for: tomeu

...kaged by Linux distributions (so it needs to work with the latest LLVM release, with no patches). Another path would be to extend clspv to cover the whole of OpenCL, but I don't know if Codeplay/Google are interested in taking such patches. Is here interest in coordinating efforts? Regards, Tomeu

> On 27 Sep 2017, at 8:21 pm, Tomeu Vizoso <tomeu.vizoso at collabora.com> wrote: > > Hi there, > > any news on coordination? We have customers who are successfully using > Mesa in their products, and that are now asking about OpenCL. None yet, I’m still waiting for IWOCL to spearhead the coordination. > M...

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

...end, etc. This proposal is only about where the collaboration would happen in the near future. If at some point we have also a backend, and people want to have it along the other backends in the main LLVM repo, that will be great. But in the meantime we need a place to work together. Regards, Tomeu > Nic > >> On 21 Feb 2018, at 4:15 pm, Tomeu Vizoso via llvm-dev <llvm-dev at lists.llvm.org> 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 &l...

...bject 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 ________________________________ From: Tom Stellard <tstellar at redhat.com> Sent: 26 February 2018 17:37 To: Anastasia Stulova; Tomeu Vizoso; llvm-dev at lists.llvm.org Cc: nd Subject: 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? > &g...

...nverter 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. Thanks, Tomeu

.... This won't help us with item (3) at all, and item (4) will be incomplete. Cheers, Anastasia ________________________________ From: llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> Sent: 23 February 2018 20:28 To: Tomeu Vizoso; LLVM Developers Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool On 02/21/2018 03:34 PM, Pierre Moreau wrote: > 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...

...-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > *From:* Tom Stellard <tstellar at redhat.com> > *Sent:* 26 February 2018 17:37 > *To:* Anastasia Stulova; Tomeu Vizoso; llvm-dev at lists.llvm.org > *Cc:* nd > *Subject:* 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 t...

On 09/27/2017 05:21 AM, Tomeu Vizoso wrote: > On 07/31/2017 02:30 PM, Nicholas Wilson via llvm-dev wrote: >> >>> On 31 Jul 2017, at 3:23 pm, Neil Henning <ll... at duskborn.com> wrote: >> >> Moving forward, other than securing the triples spirv32, spirv64, and spirvlogical from LLVM, how can...

...t; guest proxy and > host proxy <=> server communication would be standard wayland protocol. Thanks for the ideas. What I haven't understood yet is how you see the actual passing of buffers via vsock. Are you thinking of using ancillary data to pass FDs, or something else? Thanks, Tomeu

...t; guest proxy and > host proxy <=> server communication would be standard wayland protocol. Thanks for the ideas. What I haven't understood yet is how you see the actual passing of buffers via vsock. Are you thinking of using ancillary data to pass FDs, or something else? Thanks, Tomeu

...----------------------------------------------------------------------------------------------------------------- > *From:* llvm-dev <llvm-dev-bounces at lists.llvm.org> on behalf of Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> > *Sent:* 23 February 2018 20:28 > *To:* Tomeu Vizoso; LLVM Developers > *Subject:* Re: [llvm-dev] SPIRV-LLVM as an external tool > > On 02/21/2018 03:34 PM, Pierre Moreau wrote: >> 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,...

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

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

On 02/21/2018 03:34 PM, Pierre Moreau wrote: > 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. >>...

...regular LLVM releases so that it can be used by many frontends. Having an external project for assisting backends consuming SPIR-V (a la libclc) is fine but that shouldn’t mean that the processes used for generating SPIR-V need to go into a separate project. Nic > On 21 Feb 2018, at 4:15 pm, Tomeu Vizoso via llvm-dev <llvm-dev at lists.llvm.org> 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. >...

Hi Gerd and Stefan, can we reach agreement on whether vsock should be involved in this? Thanks, Tomeu On 02/07/2018 10:49 AM, Tomeu Vizoso wrote: > On 02/06/2018 03:23 PM, Gerd Hoffmann wrote: >> ?? Hi, >> >>>> Hmm?? I'm assuming the wayland client (in the guest) talks to the >>>> wayland proxy, using the wayland protocol, like it would talk to a >>...

Hi Gerd and Stefan, can we reach agreement on whether vsock should be involved in this? Thanks, Tomeu On 02/07/2018 10:49 AM, Tomeu Vizoso wrote: > On 02/06/2018 03:23 PM, Gerd Hoffmann wrote: >> ?? Hi, >> >>>> Hmm?? I'm assuming the wayland client (in the guest) talks to the >>>> wayland proxy, using the wayland protocol, like it would talk to a >>...

...fully complete and compliant OpenCL C++ support, without using any external tools. See discussion with Tom earlier. Thanks! Anastasia ________________________________ From: Chris Lattner <clattner at nondot.org> Sent: 01 March 2018 01:52 To: tstellar at redhat.com Cc: Anastasia Stulova; Tomeu Vizoso; llvm-dev at lists.llvm.org; nd Subject: Re: [llvm-dev] SPIRV-LLVM as an external tool On Feb 27, 2018, at 10:25 AM, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 02/27/2018 05:07 AM, Anastasia Stulova wrote: >>> SPIR-V does not have to be a part of LL...

On Feb 27, 2018, at 10:25 AM, Tom Stellard via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 02/27/2018 05:07 AM, Anastasia Stulova wrote: >>> SPIR-V does not have 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