On 08/16/2018 06:02 PM, Caio Marcelo de Oliveira Filho wrote:
> Hello,
>
>> +(add a new row after the exiting "atomicMax" table row, p. 179)
>> +
>> +float atomicMax(inout float mem, float data)
>> +
>> +Computes a new value by taking the maximum of the value of data and
>> +
Hello,
> +(add a new row after the exiting "atomicMax" table row, p. 179)
> +
> +float atomicMax(inout float mem, float data)
> +
> +Computes a new value by taking the maximum of the value of data and
> + the contents of mem. If one of these is an IEEE signaling NaN (i.e.,
From: Ian Romanick
v2: Describe interactions with the capabilities added by
SPV_INTEL_shader_atomic_float_minmax
v3: Remove 64-bit float support.
v4: Explain NaN issues. Explain issues with atomicMin(-0, +0) and
atomicMax(-0, +0).
Signed-off-by: Ian Romanick
---
docs/specs/INTEL_shader_atom
