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 looks like NMax works > as expected, but not NMin or NClamp.
Do you have some specific test cases that fail? > Looking at the SPIR-V/nir/intel code it's hard to tell what's going on > and whether these semantics are actually being followed. > > Any comments? > > -Brian > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
