Summary: | [bisected][regression][icl] dEQP GLES3 texsubimage3d_depth failures | ||
---|---|---|---|
Product: | Mesa | Reporter: | Clayton Craft <clayton.a.craft> |
Component: | Drivers/Gallium/Iris | Assignee: | Kenneth Graunke <kenneth> |
Status: | RESOLVED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | normal | ||
Priority: | medium | Keywords: | bisected, regression |
Version: | git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Clayton Craft
2019-08-19 17:37:59 UTC
These also seem to be failing from that commit: dEQP-GLES3.functional.texture.specification.texstorage2d.format.depth24_stencil8_2d dEQP-GLES3.functional.texture.specification.texstorage2d.format.depth32f_stencil8_2d dEQP-GLES3.functional.texture.specification.texstorage2d.format.depth_component24_2d dEQP-GLES3.functional.texture.specification.texstorage2d.format.depth_component32f_2d dEQP-GLES3.functional.texture.specification.texstorage3d.format.depth24_stencil8_2d_array dEQP-GLES3.functional.texture.specification.texstorage3d.format.depth32f_stencil8_2d_array dEQP-GLES3.functional.texture.specification.texstorage3d.format.depth_component24_2d_array dEQP-GLES3.functional.texture.specification.texstorage3d.format.depth_component32f_2d_array This should be fixed by: commit 2e1be771e47adf1d06901283ffb8df0d83f28b3c Author: Kenneth Graunke <kenneth@whitecape.org> Date: Fri Aug 23 17:32:06 2019 -0700 isl: Don't set UnormPathInColorPipe for integer surfaces. I am unclear what the underlying issue is, but setting this bit shouldn't actually do anything particularly useful for integer formats. If it introduces any precision issues, it could definitely affect our bit-for-bit copies (via blorp_copy), which was what was causing this test to fail. I verified that denying it for integer formats doesn't regress performance in Manhattan 3.0 on i965, which was the largest gain from the original patch. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.