Displaying 4 results from an estimated 4 matches for "swizll".
Did you mean:
swill
2016 Apr 08
3
[PATCH] nouveau: codegen: Take src swizzle into account on loads
...> The current nouveau impl is correct - only the .x of the address
> should be loaded, with up to 16 bytes read into the destination.
Ah note this is not about swizzling on the address, that indeed
makes no sense given how the addressing works for BUFFERS / MEMORY,
no this is about adding a swizlling postfix to the buffer / memory
resource specification, for example:
LOAD TEMP[0].y, MEMORY[0].xxxx, TEMP[0]
See the swizzling is done on the resource, not on the address, so
the swizzling specifies swizzling of the up to 16 bytes read from
address, it does not influence the address handling at...
2016 Apr 08
0
[PATCH] nouveau: codegen: Take src swizzle into account on loads
...pl is correct - only the .x of the address
>> should be loaded, with up to 16 bytes read into the destination.
>
>
> Ah note this is not about swizzling on the address, that indeed
> makes no sense given how the addressing works for BUFFERS / MEMORY,
> no this is about adding a swizlling postfix to the buffer / memory
> resource specification, for example:
>
> LOAD TEMP[0].y, MEMORY[0].xxxx, TEMP[0]
>
> See the swizzling is done on the resource, not on the address, so
> the swizzling specifies swizzling of the up to 16 bytes read from
> address, it does not...
2016 Apr 07
2
[PATCH] nouveau: codegen: Take src swizzle into account on loads
The llvm TGSI backend does things like:
LOAD TEMP[0].y, MEMORY[0].xxxx, TEMP[0].x
Expecting the data at address TEMP[0].x to get loaded to
TEMP[0].y. Before this commit the data at TEMP[0].x + 4 would be
loaded instead. This commit fixes this.
Signed-off-by: Hans de Goede <hdegoede at redhat.com>
---
src/gallium/drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp | 8 ++++++--
1 file changed,
2016 Apr 08
2
[PATCH] nouveau: codegen: Take src swizzle into account on loads
....x of the address
>>> should be loaded, with up to 16 bytes read into the destination.
>>
>>
>> Ah note this is not about swizzling on the address, that indeed
>> makes no sense given how the addressing works for BUFFERS / MEMORY,
>> no this is about adding a swizlling postfix to the buffer / memory
>> resource specification, for example:
>>
>> LOAD TEMP[0].y, MEMORY[0].xxxx, TEMP[0]
>>
>> See the swizzling is done on the resource, not on the address, so
>> the swizzling specifies swizzling of the up to 16 bytes read from
&g...