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) \
>
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, \
> G
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, \
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/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,
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 er
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 loo
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: T
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 where
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
10 matches
Mail list logo
