Intel Vulkan Driver will not keep bit patterns for floating textures
We found that on Tiger Lake and above, if we upload NaN values to a float texture and fetch the data in the shader, different NaN values are all converted to a specific qNaN (0xFFC00000). (On Kaby Lake GPUs, we do not see such behavior.) We knew that such behavior does not violate Vulkan spec, but it causes some troubles when running some 3D applications (e.g., AutoCAD 2020) in the virtual machine. We are wondering if it's possible for Tiger Lake (and above) driver to preserve bit patterns for different NaN values.