Summary: | [ILK Bisected]Piglit/shaders_glsl-bug-22603 fails | ||
---|---|---|---|
Product: | Mesa | Reporter: | lu hua <huax.lu> |
Component: | Drivers/DRI/i965 | Assignee: | Kenneth Graunke <kenneth> |
Status: | VERIFIED FIXED | QA Contact: | Intel 3D Bugs Mailing List <intel-3d-bugs> |
Severity: | major | ||
Priority: | high | CC: | idr |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
lu hua
2014-02-21 02:05:16 UTC
Following cases also fail on Ironlake with same bisect commit: spec_ARB_ES2_compatibility_FBO_blit_from_missing_attachment_(ES2_completeness_rules) spec_ARB_ES2_compatibility_FBO_blit_to_missing_attachment_(ES2_completeness_rules) spec_ARB_framebuffer_object_FBO_blit_from_missing_attachment spec_ARB_framebuffer_object_FBO_blit_to_missing_attachment spec_ARB_framebuffer_object_framebuffer-blit-levels_draw_depth spec_ARB_framebuffer_object_framebuffer-blit-levels_read_depth Whoops, looks like I failed to rebase this properly after fixing the MESA_FORMAT X8 <-> S8 mixup. Thanks for the report! Patch on the mailing list: http://lists.freedesktop.org/archives/mesa-dev/2014-February/054581.html commit 82f9ad8c6011f5c1e8fd7065eeb6094f6e16dea9 Author: Kenneth Graunke <kenneth@whitecape.org> Date: Thu Feb 20 23:08:22 2014 -0800 i965: Fix S8 and X8 reversal in brw_depthbuffer_format refactor. In commit 09d9a8913e8c28fc4c1c60d7da85a2f093786894, I accidentally botched the X8 and S8 cases. (I wrote this patch before realizing that X8 and S8 had been swapped in the big MESA_FORMAT rename, and apparently didn't rebase it properly after fixing that...) Fixes regressions in 13 Piglit tests on Ironlake. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=75291 Signed-off-by: Kenneth Graunke <kenneth@whitecape.org> Reviewed-by: Jordan Justen <jordan.l.justen@intel.com> Reviewed-by: Ian Romanick <ian.d.romanick@intel.com> Verified.Fixed. |
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.