On 08/21/2018 06:10 AM, Axel Davy wrote:
> On 23/06/2018 07:03, Ian Romanick wrote:
>> I initially started implementing support for NV_shader_atomic_float. I
>> had misunderstood the hardware specs, and Intel hardware cannot actually
>> do that extension. It does have some floating-point atomic
On 23/06/2018 07:03, Ian Romanick wrote:
I initially started implementing support for NV_shader_atomic_float. I
had misunderstood the hardware specs, and Intel hardware cannot actually
do that extension. It does have some floating-point atomic support, so
I decided to create an extension based
> The code is here:
>
>
> https://cgit.freedesktop.org/~idr/mesa/log/?h=INTEL_shader_atomic_float_minmax
The series is
Reviewed-by: Caio Marcelo de Oliveira Filho
I'd consider adding some clarification about not quietizing sNaN
and/or relaxing the definition in the spec (patch 3).
>
bump.
I've pushed a rebased version of the branch to the cgit below.
On 06/22/2018 10:03 PM, Ian Romanick wrote:
> I initially started implementing support for NV_shader_atomic_float. I
> had misunderstood the hardware specs, and Intel hardware cannot actually
> do that extension. It does have
I initially started implementing support for NV_shader_atomic_float. I
had misunderstood the hardware specs, and Intel hardware cannot actually
do that extension. It does have some floating-point atomic support, so
I decided to create an extension based on what the hardware actually can
do. I
