On 11/17/2020 01:59 PM, Brian Paul wrote:
On 11/17/2020 11:45 AM, Ian Romanick wrote:
On 11/17/20 9:25 AM, Brian Paul wrote:
It appears these SPIR-V extension functions don't behave as they should
on Intel (don't know about other Vulkan drivers).
They're supposed to be NaN-aware such that if
On 11/17/2020 11:45 AM, Ian Romanick wrote:
On 11/17/20 9:25 AM, Brian Paul wrote:
It appears these SPIR-V extension functions don't behave as they should
on Intel (don't know about other Vulkan drivers).
They're supposed to be NaN-aware such that if one argument is NaN, the
other argument is
On 11/17/20 9:25 AM, Brian Paul wrote:
>
> It appears these SPIR-V extension functions don't behave as they should
> on Intel (don't know about other Vulkan drivers).
>
> They're supposed to be NaN-aware such that if one argument is NaN, the
> other argument is returned. From our testing, it
: Tuesday, November 17, 2020 9:25:01 AM
To: mesa-dev@lists.freedesktop.org
Subject: [Mesa-dev] GLSLstd450NMin/NMax/NClamp
It appears these SPIR-V extension functions don't behave as they should
on Intel (don't know about other Vulkan drivers).
They're supposed to be NaN-aware such that if one
It appears these SPIR-V extension functions don't behave as they should
on Intel (don't know about other Vulkan drivers).
They're supposed to be NaN-aware such that if one argument is NaN, the
other argument is returned. From our testing, it looks like NMax works
as expected, but not NMin
