Summary: | [PNV Bisected]Piglit spec/glsl-1.10/execution/variable-indexing/fs-temp-mat4-col-row-wr fail | ||
---|---|---|---|
Product: | Mesa | Reporter: | lu hua <huax.lu> |
Component: | Drivers/DRI/i915 | Assignee: | Ian Romanick <idr> |
Status: | VERIFIED FIXED | QA Contact: | |
Severity: | major | ||
Priority: | medium | CC: | xunx.fang |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
lu hua
2013-05-15 02:02:22 UTC
Ian, can you reproduce? I can confirm the bisect - it works before that commit, and fails on it. I also observed that it works with either no_rast=true or LIBGL_ALWAYS_SOFTWARE=1, so presumably the Mesa IR being generated is good. Sounds like the i915 assembly is bad. I don't plan on investigating further, though...the i915c driver confuses me. I suspect the problem is changing the compiler to not generate the vectorized compares makes it take too many instructions for i915. That's just a hunch, though. I will take care of this for 9.2. It turned out to be the opposite of my intuition. The changes in the patch caused *more* tests to run in hardware on i915. The problem is the tests require more precision that i915 can deliver with its 24-bit floats. I have sent a patch to the piglit mailing list to relax the precision requirement (these tests are not about the precision of the distance() function anyway!) and a patch to the Mesa list that makes even more tests run in hardware. http://lists.freedesktop.org/archives/piglit/2013-August/006903.html http://lists.freedesktop.org/archives/mesa-dev/2013-August/043650.html I am removing this bug from the release tracker because it's not a real regression. Please confirm that this is seen on an SNB or newer platform. (In reply to comment #5) > Please confirm that this is seen on an SNB or newer platform. It passes on all platforms. Test on latest mesa master branch. Fixed. Verified. |
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.