Am 20.03.2013 19:09, schrieb Christoph Bumiller:
> On 20.03.2013 18:30, Roland Scheidegger wrote:
>> Am 20.03.2013 17:46, schrieb Christoph Bumiller:
>>> On 20.03.2013 17:05, Roland Scheidegger wrote:
Not sure I fully understand this, but I'm thinking "whenever in doubt,
use somethin
On 20.03.2013 18:30, Roland Scheidegger wrote:
> Am 20.03.2013 17:46, schrieb Christoph Bumiller:
>> On 20.03.2013 17:05, Roland Scheidegger wrote:
>>>
>>> Not sure I fully understand this, but I'm thinking "whenever in doubt,
>>> use something close to what dx10 does" since that's likely going to
Am 20.03.2013 17:46, schrieb Christoph Bumiller:
> On 20.03.2013 17:05, Roland Scheidegger wrote:
>> Am 20.03.2013 15:41, schrieb Christoph Bumiller:
>>> Sorry, this has become longer than I anticipated ...
>>>
>>> I've been toying with adding support for TGSI_FILE_INPUT/OUTPUT arrays
>>> because,
On 20.03.2013 17:05, Roland Scheidegger wrote:
> Am 20.03.2013 15:41, schrieb Christoph Bumiller:
>> Sorry, this has become longer than I anticipated ...
>>
>> I've been toying with adding support for TGSI_FILE_INPUT/OUTPUT arrays
>> because, since I cannot allocate varyings in the same order that
Am 20.03.2013 15:41, schrieb Christoph Bumiller:
> Sorry, this has become longer than I anticipated ...
>
> I've been toying with adding support for TGSI_FILE_INPUT/OUTPUT arrays
> because, since I cannot allocate varyings in the same order that the
> register index specifies, I need it:
>
> ===
Sorry, this has become longer than I anticipated ...
I've been toying with adding support for TGSI_FILE_INPUT/OUTPUT arrays
because, since I cannot allocate varyings in the same order that the
register index specifies, I need it:
===
EXAMPLE:
OUT[0], CLIPDIST[1], must be allocated at address 0x2c
