-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/14/2011 12:18 PM, Dave Airlie wrote:
>>> Hi guys,
>>>
>>> So I've been noticing there are a number of inconsistencies
>>> between EXT_gpu_shader4 and GLSL1.30, are you planning on
>>> implementing EXT_gpu_shader4?
>>>
>>> EXT_gpu_shader4 appe
>> Hi guys,
>>
>> So I've been noticing there are a number of inconsistencies
>> between EXT_gpu_shader4 and GLSL1.30, are you planning on
>> implementing EXT_gpu_shader4?
>>
>> EXT_gpu_shader4 appears to define "unsigned" and can also use
>> texture2D to sample from integer samplers.
>
> There are
On 09/14/2011 06:16 AM, Dave Airlie wrote:
Hi guys,
So I've been noticing there are a number of inconsistencies between
EXT_gpu_shader4 and GLSL1.30, are you planning on implementing
EXT_gpu_shader4?
I'm not super interested in it, though it seems like a nice thing to
have once GL3 and GLSL 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/14/2011 06:16 AM, Dave Airlie wrote:
> Hi guys,
>
> So I've been noticing there are a number of inconsistencies
> between EXT_gpu_shader4 and GLSL1.30, are you planning on
> implementing EXT_gpu_shader4?
>
> EXT_gpu_shader4 appears to define "u
Hi guys,
So I've been noticing there are a number of inconsistencies between
EXT_gpu_shader4 and GLSL1.30, are you planning on implementing
EXT_gpu_shader4?
EXT_gpu_shader4 appears to define "unsigned" and can also use
texture2D to sample from integer samplers.
My main worry is we end up needing