Displaying 3 results from an estimated 3 matches for "tgsi64".
Did you mean:
tgsi
2016 Feb 23
2
Dealing with opencl kernel parameters in nouveau now that RES support is gone
...> something good for that, if it does we can use semantic indices on the
> GLOBAL to make it like
>
> DCL MEMORY[0], GLOBAL[0]
> DCL MEMORY[1], GLOBAL[1]
>
> etc. But again, this is pretty optional.
I think that for Tesla we can just only support the tgsi32 target
and not the tgsi64 target, at least that is how I envision things
today, who knows what tomorrow will bring :)
Regards,
Hans
2016 Feb 23
0
Dealing with opencl kernel parameters in nouveau now that RES support is gone
...we can use semantic indices on the
> >GLOBAL to make it like
> >
> >DCL MEMORY[0], GLOBAL[0]
> >DCL MEMORY[1], GLOBAL[1]
> >
> >etc. But again, this is pretty optional.
>
> I think that for Tesla we can just only support the tgsi32 target
> and not the tgsi64 target, at least that is how I envision things
> today, who knows what tomorrow will bring :)
Fermi is the first family supporting 64 bit addresses, on top of 32 bit
addresses, while Kepler can only do 64 bit IIRC (or is it Maxwell which dropped
the 32 bit support?).
Regards,
Pierre
>
>...
2016 Feb 22
2
Dealing with opencl kernel parameters in nouveau now that RES support is gone
Hi,
On 22-02-16 17:13, Ilia Mirkin wrote:
> On Mon, Feb 22, 2016 at 11:00 AM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
>> On Mon, Feb 22, 2016 at 10:50 AM, Hans de Goede <hdegoede at redhat.com> wrote:
>>>> But assuming I'm right, what I'm proposing is that instead of passing
>>>> the input in as a global buffer, to instead pass it in as a