I have been thinking about this more and I actually like the way
OpenGL does it. The indexing with InvocationID can be lowered with a
copy propagation pass for drivers that cannot do it - or they can just
ignore the innermost index and assume it's always equal to
InvocationID. I also prefer having
Am 16.09.2014 19:40, schrieb Marek Olšák:
> On Tue, Sep 16, 2014 at 7:31 PM, Roland Scheidegger
> wrote:
>> Am 16.09.2014 18:41, schrieb Ilia Mirkin:
>>> On Tue, Sep 16, 2014 at 12:29 PM, Marek Olšák wrote:
On Tue, Sep 16, 2014 at 5:42 PM, Ilia Mirkin wrote:
> OK, so just to summarize:
On Tue, Sep 16, 2014 at 7:31 PM, Roland Scheidegger wrote:
> Am 16.09.2014 18:41, schrieb Ilia Mirkin:
>> On Tue, Sep 16, 2014 at 12:29 PM, Marek Olšák wrote:
>>> On Tue, Sep 16, 2014 at 5:42 PM, Ilia Mirkin wrote:
OK, so just to summarize:
The approach suggested by Roland is to h
Am 16.09.2014 18:41, schrieb Ilia Mirkin:
> On Tue, Sep 16, 2014 at 12:29 PM, Marek Olšák wrote:
>> On Tue, Sep 16, 2014 at 5:42 PM, Ilia Mirkin wrote:
>>> OK, so just to summarize:
>>>
>>> The approach suggested by Roland is to have the outputs be
>>> one-dimensional and only representing the cu
Am 16.09.2014 18:29, schrieb Marek Olšák:
> On Tue, Sep 16, 2014 at 5:42 PM, Ilia Mirkin wrote:
>> OK, so just to summarize:
>>
>> The approach suggested by Roland is to have the outputs be
>> one-dimensional and only representing the current invocation's
>> per-vertex outputs. Each invocation wou
On Tue, Sep 16, 2014 at 6:41 PM, Ilia Mirkin wrote:
> On Tue, Sep 16, 2014 at 12:29 PM, Marek Olšák wrote:
>> On Tue, Sep 16, 2014 at 5:42 PM, Ilia Mirkin wrote:
>>> OK, so just to summarize:
>>>
>>> The approach suggested by Roland is to have the outputs be
>>> one-dimensional and only represen
On Tue, Sep 16, 2014 at 12:29 PM, Marek Olšák wrote:
> On Tue, Sep 16, 2014 at 5:42 PM, Ilia Mirkin wrote:
>> OK, so just to summarize:
>>
>> The approach suggested by Roland is to have the outputs be
>> one-dimensional and only representing the current invocation's
>> per-vertex outputs. Each in
On Tue, Sep 16, 2014 at 5:42 PM, Ilia Mirkin wrote:
> OK, so just to summarize:
>
> The approach suggested by Roland is to have the outputs be
> one-dimensional and only representing the current invocation's
> per-vertex outputs. Each invocation would also get access to other
> invocations' per-ve
OK, so just to summarize:
The approach suggested by Roland is to have the outputs be
one-dimensional and only representing the current invocation's
per-vertex outputs. Each invocation would also get access to other
invocations' per-vertex outputs via a 2d input array.
So a shader might look somet
Am 01.09.2014 18:53, schrieb Ilia Mirkin:
> On Mon, Sep 1, 2014 at 12:47 PM, Roland Scheidegger
> wrote:
>> Am 01.09.2014 18:19, schrieb Ilia Mirkin:
>>> On Mon, Sep 1, 2014 at 12:00 PM, Roland Scheidegger
>>> wrote:
Am 29.08.2014 22:44, schrieb Ilia Mirkin:
> Hello,
>
> I've b
On Mon, Sep 1, 2014 at 12:47 PM, Roland Scheidegger wrote:
> Am 01.09.2014 18:19, schrieb Ilia Mirkin:
>> On Mon, Sep 1, 2014 at 12:00 PM, Roland Scheidegger
>> wrote:
>>> Am 29.08.2014 22:44, schrieb Ilia Mirkin:
Hello,
I've been thinking a bit about how to properly implement TCS
Am 01.09.2014 18:19, schrieb Ilia Mirkin:
> On Mon, Sep 1, 2014 at 12:00 PM, Roland Scheidegger
> wrote:
>> Am 29.08.2014 22:44, schrieb Ilia Mirkin:
>>> Hello,
>>>
>>> I've been thinking a bit about how to properly implement TCS outputs
>>> in TGSI. As a quick reminder, there are per-vertex (i.e
On Mon, Sep 1, 2014 at 12:00 PM, Roland Scheidegger wrote:
> Am 29.08.2014 22:44, schrieb Ilia Mirkin:
>> Hello,
>>
>> I've been thinking a bit about how to properly implement TCS outputs
>> in TGSI. As a quick reminder, there are per-vertex (i.e. invocation)
>> and per-patch outputs in TCS. And w
Am 29.08.2014 22:44, schrieb Ilia Mirkin:
> Hello,
>
> I've been thinking a bit about how to properly implement TCS outputs
> in TGSI. As a quick reminder, there are per-vertex (i.e. invocation)
> and per-patch outputs in TCS. And while you can only write to the
> current invocation's per-vertex o
Hello,
I've been thinking a bit about how to properly implement TCS outputs
in TGSI. As a quick reminder, there are per-vertex (i.e. invocation)
and per-patch outputs in TCS. And while you can only write to the
current invocation's per-vertex outputs, you can read from any of
them. (With barrier()
15 matches
Mail list logo