Displaying 4 results from an estimated 4 matches for "spirv32".
2017 Sep 27
0
[SPIR-V] SPIR-V in LLVM
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 we go about coordinating efforts? I feel that having one backend is a better use of everybody’s time than having three. If we don't get around to anything I’m sure we can organise something at IWOCL.
>
> Hi there,
>
> any news on coord...
2017 Jul 31
0
[SPIR-V] SPIR-V in LLVM
...and then bitcast the value instead). I am not a backend person - it'd be useful to me if anyone who is a backend person could tell me if the type legalization could handle this in a 'real' backend?
Sorry I’m not a backend person either.
Moving forward, other than securing the triples spirv32, spirv64, and spirvlogical from LLVM, how can we go about coordinating efforts? I feel that having one backend is a better use of everybody’s time than having three. If we don't get around to anything I’m sure we can organise something at IWOCL.
Nic
(Sorry forgot to hit reply all last time)
2017 Sep 27
4
[SPIR-V] SPIR-V in LLVM
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 we go about coordinating efforts? I feel that having one backend is a better use of everybody’s time than having three. If we don't get around to anything I’m sure we can organise something at IWOCL.
Hi there,
any news on coordination? We have cus...
2017 Jul 18
3
[SPIR-V] SPIR-V in LLVM
Yet another implementation of the backend, heh.
I’d just started in earnest writing a tablegen based one, with the main goal of fixing the intrinsics to actually be intrinsics.
I think it would be a good idea to join forces with the folk at KhronosGroup and consolidate the work done for inclusion into LLVM.
Nic
> On 17 Jul 2017, at 9:55 pm, Neil Henning via llvm-dev <llvm-dev at