Summary: | [ILK Bisected]some piglit and ogles2conform cases fail | ||
---|---|---|---|
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: | medium | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
lu hua
2014-06-13 02:18:00 UTC
Please confirm that this is seen on SNB or newer platforms. (In reply to comment #1) > Please confirm that this is seen on SNB or newer platforms. It only happens on ILK platform, Works well on SNB+ platforms. Patch on mailing list: http://lists.freedesktop.org/archives/mesa-dev/2014-August/065928.html (In reply to comment #3) > Patch on mailing list: > http://lists.freedesktop.org/archives/mesa-dev/2014-August/065928.html Fixed by this patch. commit 97d03b9366bfa55b27feb92aa5afacd9c5f6f421 Author: Kenneth Graunke <kenneth@whitecape.org> Date: Sat Aug 16 15:18:21 2014 -0700 i965: Disable try_emit_b2f_of_compare on Gen4-6. The optimization relies on CMP setting the destination to 0, which is equivalent to 0.0f. However, early platforms only set the least significant byte, leaving the other bits undefined. So, we must disable the optimization on those platforms. Oddly, Sandybridge wasn't reported as broken. The PRM states that it only sets the LSB, but the internal documentation says that it follows the IVB behavior. Since it wasn't reported as broken, we believe it really does follow the IVB behavior. v2: Allow the optimization on Sandybridge (requested by Matt). +32 piglits on Ironlake. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?=79963 Signed-off-by: Kenneth Graunke <kenneth@whitecape.org> Reviewed-by: Chris Forbes <chrisf@ijw.co.nz> Reviewed-by: Matt Turner <mattst88@gmail.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.