Re: [Mesa-dev] fp/int64 on gen11/12?

2020-11-17 Thread Jason Ekstrand
On Tue, Nov 17, 2020 at 6:10 PM Jordan Justen wrote: > > On 2020-11-17 16:03:31, Brian Paul wrote: > > Another Intel question: It looks like gen11/gen12 don't have fp/int64 > > enabled in the Vulkan driver. From gen_device_info.c: > > > > #define GEN11_FEATURES(_gt, _slices, _subslices, _l3) \ >

Re: [Mesa-dev] fp/int64 on gen11/12?

2020-11-17 Thread Jordan Justen
On 2020-11-17 16:03:31, Brian Paul wrote: > Another Intel question: It looks like gen11/gen12 don't have fp/int64 > enabled in the Vulkan driver. From gen_device_info.c: > > #define GEN11_FEATURES(_gt, _slices, _subslices, _l3) \ > GEN8_FEATURES, \ >

[Mesa-dev] fp/int64 on gen11/12?

2020-11-17 Thread Brian Paul
Another Intel question: It looks like gen11/gen12 don't have fp/int64 enabled in the Vulkan driver. From gen_device_info.c: #define GEN11_FEATURES(_gt, _slices, _subslices, _l3) \ GEN8_FEATURES, \ GEN11_HW_INFO, \

Re: [Mesa-dev] GLSLstd450NMin/NMax/NClamp

2020-11-17 Thread Brian Paul
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

Re: [Mesa-dev] SpvOpSelect w/ float operands

2020-11-17 Thread Brian Paul
On 11/17/2020 11:49 AM, Ian Romanick wrote: On 11/17/20 9:25 AM, Brian Paul wrote: Using the Intel Vulkan driver, we've found some cases where SpvOpSelect is returning -0.0 (negative zeros) instead of normal 0.0 depending on the arguments. Do you have a specific test case that fails? Yeah,

Re: [Mesa-dev] SpvOpSelect w/ float operands

2020-11-17 Thread Ian Romanick
On 11/17/20 9:25 AM, Brian Paul wrote: > > Using the Intel Vulkan driver, we've found some cases where SpvOpSelect > is returning -0.0 (negative zeros) instead of normal 0.0 depending on > the arguments. Do you have a specific test case that fails? It seems like on some platforms there was an

Re: [Mesa-dev] GLSLstd450NMin/NMax/NClamp

2020-11-17 Thread Ian Romanick
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

Re: [Mesa-dev] GLSLstd450NMin/NMax/NClamp

2020-11-17 Thread Oliveira, Caio
Brian, There are some NaN related fixes by Ian soon to be merged in https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/6358. Could you check if the MR helps this and the Select issue? Thanks, Caio From: mesa-dev on behalf of Brian Paul Sent:

[Mesa-dev] SpvOpSelect w/ float operands

2020-11-17 Thread Brian Paul
Using the Intel Vulkan driver, we've found some cases where SpvOpSelect is returning -0.0 (negative zeros) instead of normal 0.0 depending on the arguments. I'm wondering if "SpvOpSelect x, a, b" for floats is being implemented with something like "a*x + b*(1-x)" ? That might explain

[Mesa-dev] GLSLstd450NMin/NMax/NClamp

2020-11-17 Thread Brian Paul
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